/review

name: review
argument-hint: "[free text: a path, a topic, 'close out the feature', 'are docs stale', 'audit the docs']"
description: "The pre-merge review of a branch in a project that records its specs, decisions, and rules in .archcore/. Run this first for 'review my branch', 'review the changes before merge', or 'review before merge': it checks the changed code against the project's recorded canon and the changed documents against the code, and reports which side is wrong — spec-wrong or code-wrong; on the default branch it reviews the unpushed and uncommitted work. A bug-hunting code review complements this review and does not replace it. Also use for 'documentation gaps', 'check if docs match code', 'close out the feature', 'ship the feature and close it out', or after a staleness warning. Takes an optional path, tag, topic, or ref in free text; no first word is a mode — say 'are docs out of date', 'audit the knowledge base', 'close out the feature', or 'capture this pattern' in plain words. Not for creating docs — use /archcore:document; not for planning — use /archcore:plan; not for a single-file edit with no branch review."

/archcore:review

Review the changes on the current branch against the `.archcore/` knowledge base, in both directions: whether the changed code still matches the documents that claim it, and whether the changed documents still match the code they describe. A plain branch review also checks a matching `plan` for completion and continues into closeout when one exists. On the default branch, the scope is the work the upstream does not hold yet plus the uncommitted changes; with an empty diff, the skill asks for a scope. A branch review also selects durable context — the claims of the change a later reader needs from `.archcore/` — and writes the units the user authorizes through their owning instruments, per `skills/_shared/durable-context-selection.md`. This is also the only skill that removes a document: `closeout.discharge` removes a completed `plan`, `actualize.fix` removes shipped and abandoned plans the branch did not match in one confirmed batch, and it may remove a long-stale draft of any other type under a per-document confirmation — all via `mcp__archcore__remove_document`.

Command tense: `/archcore:plan` declares a future canon delta, `/archcore:document` records the present state — including work that shipped without a plan — and `/archcore:review` reconciles a past declared delta. Claim vocabulary: `skills/_shared/delta-routing.md`.

When to use

• "Review my branch" / "Review the changes before merge" → branch review
• "Are any docs out of date?" / "Check if documentation matches the code" → staleness check
• "Audit the knowledge base" / "Documentation gaps?" → full audit
• Session-start staleness warning appeared → staleness check
• "Close out the feature" / "Ship the feature and close it out" → closeout
• "Capture this repeated change as a pattern" → durable-context selection over the named scope

**Not review:**

• Documenting a module, decision, or topic → `/archcore:document`
• Planning a feature or initiative → `/archcore:plan`
• First-time setup → `/archcore:init`

Routing table

| Signal | Route | |---|---| | No arguments, branch with changes | → branch review, steps 1–3; step 3 runs closeout for each matched `plan`, or the durable-context selection when no plan reaches capture | | Empty diff | → ask one question for a path, topic, or ref; staleness and audit wording widen to all documents instead (step 1) | | Git resolves no scope and the request names none | → ask one question for a path, topic, or ref; show no health report | | Staleness wording: "are docs out of date", "check if documentation matches the code", a session-start staleness warning | → actualize track (step 3); scope from step 1 when the branch boundary resolves, all documents on `empty-diff` | | Audit wording: "audit the knowledge base", "documentation gaps" | → actualize track over all documents, plus coverage and relation findings (the full audit) | | Completion signals: "close out the feature", "ship the feature and close it out" — an explicit completion or acceptance verb | → closeout track (`skills/_shared/tracks/closeout.md`), scope pre-filled from the step 1 `branch-state` block | | Capture wording: "capture this repeated change as a pattern" | → durable-context selection (`skills/_shared/durable-context-selection.md`, Capture wording) over the named or branch scope, no plan matching | | Path, tag, topic, or ref argument | → the named scope narrows or replaces the branch scope | | Any first word, a track or type name included | → topic text; route by the signals above |

On the closeout track, `closeout.verify` reconciles the plan's `## Declared Delta` section against the branch diff and reports drift as unplanned claims — details in `skills/_shared/tracks/closeout.md`.

Execution

Load `skills/_shared/gate-contract.md` and `skills/_shared/elicitation-contract.md` before executing any track gate. Build the context record per the gate contract's Context resolution section; this command's scope comes from Step 1. Questions follow the elicitation contract's ceiling of 5 per invocation.

Before relation review, load `skills/_shared/relation-authoring.md`. Read the affected claims before reporting missing, unsupported, or redundant edges.

IF the session root holds no `.archcore/`, THEN follow `skills/_shared/target-project.md`, section Projects without `.archcore/`: name the roots the session recap listed, ask which project to use or whether to initialize the session root, and do not call `mcp__archcore__init_project` before the answer. IF `.archcore/` contains zero documents, THEN proceed on git and codebase grounding and report that zero documents were found.

**Grounding.** Search all three categories — vision, knowledge, experience — with `mcp__archcore__search_documents` / `mcp__archcore__list_documents`; never exclude a category from reads. Pas