spec-spine: Skill for Claude Code

/code-review: correctness, spec drift, invariants

Reviews the current diff against three questions: does the change have correctness or edge-case bugs, does it still match its owning spec's contract, and does it hold the invariants the project's path-scoped rules name. Output is an evidence-oriented findings list, each line citing file:line. Nothing authored is modified. The gate's read-only forms (scripts/statecraft/gate.sh governance, which includes the composed freshness read) are used so the review never dirties the tree; a stale verdict is itself a finding.

Step 0: scope the diff

git fetch origin
BASE="$(git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null || echo origin/main)"   # spec 093: resolved, not assumed
git status --short && git diff --stat && git log --oneline -10
git diff "$BASE"...HEAD --stat        # committed delta
git diff HEAD --stat                  # uncommitted delta
git diff "$BASE"...HEAD --name-only; git diff HEAD --name-only

Note which classes changed: source, specs (specs/**/spec.md), standards (standards/**), the harness (.claude/**, AGENTS.md, CLAUDE.md, workflows), scripts, docs, derived shards.

Step 1: the gate stays green

sh scripts/statecraft/gate.sh governance
BASE_SHA="$(git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null || echo origin/main)" \
  HEAD_SHA=HEAD PR_BODY="${PR_BODY:-}" sh scripts/statecraft/gate.sh couple

then the stack's own build, tests, and lints as AGENTS.md lists them.

• A couple failure is the headline finding: cite the file the gate named and the owning spec whose declared edges fail to cover it.
• An unclaimed file from coverage is a finding against the implementing spec's establishes.
• A lint or freshness failure from governance mode is a corpus finding: cite the diagnostic verbatim. Stale shards mean the change forgot to run compile and index and commit the result; the fix is to do that, not to hide it.

Step 2: spec-contract match