check git:20260920.81f1ca7B

Immutable. This exact content never changes and is served at /api/v1/blob/fe90243118d68224.

---
description: Run a check on the conformance of a project or the engine with the conventions — bare = check roster
argument-hint: "[check] [project-slug]"
---

Checks live as `.claude/agents/check-<name>.md` — one isolated agent
per check, each defined by what it verifies, said in its
`description`; the roster is the scan of those files. Adding a check
means adding an agent file from `templates/check.md`; this command
does not change (who creates a check, and when: CLAUDE.md, Isolated
reviewers).

Shared behaviour: the contract skill named in each check file's
front-matter (CLAUDE.md, Isolated reviewers). Unlike the critic and
the challenger, a check files nothing: the report returns to the
session and its findings are settled there. This command only
chooses the check, passes the target and presents the report.

**Bare `/check` — the roster.** List the available checks (scan
`.claude/agents/check-*.md`, their `description` fields — each says
when it fits) and recommend which fits the moment; what a save or a
release runs is `/save`'s and `/release`'s to say. A recommendation,
never a gate; no check runs on Claude's own judgement.

**`/check <name> [slug]` — run it.** The target is a project by its
slug (the engine's own project is `forge`) or the engine root; which
of the two a check takes, and what a missing or an added slug means
to it, is its Lens section's to say — read it there. Invoke the
`check-<name>` subagent (Agent tool, session model) with the target
path and nothing else — no summary of the working conversation, no
explanation of what was meant; its isolation is the point
(POS.0930). More than one check on one target may be launched at
once and awaited together.

When it returns:
1. Present the report to the principal as it came: the one-line
   verdict, then the findings in their ranking, compactly.
2. Offer at once every finding marked "immediate fix" as one step
   (CLAUDE.md, Working methods, Step by step); apply on his word.
3. End by offering a **walkthrough** of the remaining findings
   (`.claude/skills/walkthrough/SKILL.md`, the one owner of its
   shape). Verdict vocabulary here: **fix** (agreed here, written
   once at the round's end), **defer** (recorded in the project's ledger
   under "Waiting on principal"), **accept** (the state stays as it
   is; a rule worth changing goes to the intent). Nothing blocks
   (POS.0430): a release may proceed with a finding deferred.

Do not judge substance or document quality — that is `/critique` and
`/challenge` territory. A check verifies conformance only.