@xforge/cli
v0.7.20
Published
Git-native control plane for governed AI-assisted software development
Maintainers
Readme
@xforge/cli
Git-native control plane for governed, AI-assisted software development.
XForge keeps specifications, workflow state, engineering rules, quality evidence, approvals, and audit history as versioned project facts. It projects project-owned Skills, agents, policies, and hooks to Codex, Claude Code, Cursor, OpenCode, and GitHub Copilot without becoming another Agent runtime.
Requirements
- Node.js 20 or newer
- npm 7 or newer
Install
Install an exact version in the target project:
npm install --save-dev --save-exact @xforge/[email protected]
xforge version --textThe npm package contains the CLI, protocol Schemas, and its exact verified Scaffold. Initialize a project and project one Agent-tool target in a single collision-safe operation:
xforge init --target codex --dry-run
xforge init --target codexUse --language en or --language zh-CN to select the installed Skill and
sub-Agent instruction language. Without an explicit choice, init uses the
system locale; if detection fails it prompts on an interactive terminal and
otherwise exits with an actionable language-selection diagnostic. All other
Scaffold assets are English.
Alternatively, run init without a target, review and customize
xforge/manifest.yaml, then run xforge install --target <target> for each
tool. Source checkouts, local tarballs, Git/HTTP Scaffold distributions, and
source-built installation are not supported.
Follow the Agent installation
runbook for the
full npm-only procedure. Generated runtime Hooks invoke xforge
xforge from the project root, resolving the exact local package without a
network fallback.
Quick check
From an initialized XForge project:
xforge state --text
xforge install --target codex --dry-run --text
xforge check --textJSON is the default output. --text changes presentation only; it does not
change command semantics or exit status.
Main capabilities
- Quick, Solid, and Major spec-driven Flows
- Managed projections for five Agent tools
- Constitution, Rules, PermissionPolicies, Hooks, Gates, and Approvals
- Guarded Stage transitions and revision-bound Evidence
- Signed approval receipts and append-only Audit
- Governed work-package dispatch and delivery verification
- Conflict-safe install, sync, update, and uninstall
- Atomic delta-Spec Archive
- Protocol 1 Portable-read migration support
- Read-only reporting: an in-flight Change portfolio via
xforge-status, andxforge-kanbanoutside the Change lifecycle
Run xforge help --text for the complete command list. Project documentation
lives in the XForge repository and is
written in Simplified Chinese: start from the
documentation index,
or go straight to
concepts and architecture
and the governance model.
Important boundary
XForge controls repository workflow state and evidence. It does not host model processes, make unequal Agent platforms equivalent, or authorize application deployment and production access.
