Home

SpecGit Wiki

SpecGit is a lightweight delivery binding and acceptance tool for teams and coding agents. It connects a branch or worktree, one or more issues, one PR/MR, and the project's required checks, then verifies their Git and platform evidence.

Acceptance and completion are separate facts. specgit finish exit 0 means accepted. A delivery is completed only after its merge and every bound issue closure are confirmed. Missing evidence yields unknown; it never grants acceptance. The command itself is read-only.

Keep verification proportional

A README introduction or ordinary project-guidance edit needs a relevant content review and lightweight checks. It does not need product builds, full tests, mutation testing, repeated agent reviews, or a package release. Source and executable inputs use their applicable product checks. A mixed PR still needs product verification.

SpecGit's own repository retains lightweight remote metadata validation and acceptance before merge. Adopting projects choose their own check scope; the source repository's CI policy is not imposed on their business pipelines.

Start here

Guide	What it explains
Getting Started	Install, initialize, deliver, and upgrade
CLI Reference	Ten commands, flags, exit codes, and JSON
Concepts	Binding, evidence, acceptance, and completion
Team Workflow	Policy, proportional verification, review, and merge
GitLab Support	Host declaration, compatibility, and pipeline ownership
Provider Architecture	Local Git and forge capabilities

Install with npm install -g specgit@latest; requirements are Node.js >=20.19, Git, and an authenticated gh or glab. Use specgit --version to identify the installed runtime. These pages describe v1.14.0 (pending release), including its default-branch evidence requirements. The registry's latest release was v1.13.1 when checked on 2026-09-05.

Detailed contracts live in the repository docs. The editable Wiki copies are maintained under docs/wiki/; publishing them to this separate Wiki is an explicit step.

中文：首页 · 快速开始