ai-blueprint: Skill for Claude Code

audit - review code quality against the project standards

Context reuse: Reuse any required file already loaded in project instructions or the current session. Read it again only if absent, changed, or exact current bytes or line references are needed.

First action: Before project inspection, preflight, or any other tool call, publish running to blueprint/.state/run.json when blueprint/.state/ exists. From the project root, run the first helper that exists, node .agents/skills/blueprint-doctor/scripts/run-state.mjs or node .claude/skills/blueprint-doctor/scripts/run-state.mjs, with start --command <skill> --summary "<truthful summary>" --boundary <read-only|reviewed|local-only>. Use update at milestones, with --status blocked --resume <command> for a blocker, and finish --status ready|completed at the end; --help lists every option and blueprint/workflow.md has the full activity contract. A missing or failing helper is a warning, not a blocker.

Where this sits in the workflow:

/implement or /autopilot  ->  [audit]  ->  fixes or /complete
(code exists)                 (review +    (repair quality issues
                               ledger)      or close the feature)

/check proves behavior against the spec. /blueprint-doctor checks Blueprint setup and workflow health. This skill checks the code itself through either a broad review or one focused lens: quality, security, performance, or tests.

It reviews code without changing it: it never edits source files, installs dependencies, commits, merges, pushes, or starts product work. A normal audit's one write is the findings ledger at blueprint/context/findings.md (Step 4), the durable record of findings and their status. Independent mode may also write blueprint/context/review.md using the exact record contract in reference/independent-review.md.

The quality-gate config controls when another workflow invokes this skill automatically. An explicit /audit or $audit request always selects the audit regardless of whether the applicable gate is manual, conditional, or always. A selected independentReview gate invokes independent mode instead of letting the builder satisfy its own review. When both audit and independent review are selected, one passing independent review satisfies the audit gate. A missing config means built-in defaults. If it exists but is invalid, stop and point to /blueprint-doctor before writing the findings ledger.