review-change

--no-check

Steps

1. Pin the diff. The fixed point defaults to the merge-base of

   HEAD

   and the default branch;

   HEAD

   means uncommitted work only. Resolve it with

   git rev-parse --verify <ref>^{commit}

   and stop if it fails. The change is everything from the fixed point to the working tree, untracked files included:

   git diff --name-only <fixed-point>

   plus

   git ls-files --others --exclude-standard

   . Drop untracked dependency installs and build output, and remember them for the report. An empty list ends the skill: say there is nothing to review.
2. Find the standards, all of them, in precedence order: paths passed as arguments,

   .agents/coding-standards.md

   ,

   CODING_STANDARDS.md

   ,

   CONTRIBUTING.md

   and any other doc on how to write code here (not a user manual, product doc, or brand guide). Also collect the linter, formatter and type-checker configs the project's check command uses (not build or test-runner configs), and every

   AGENTS.md

   and

   CLAUDE.md

   at the root or in a touched directory. No standards at all is normal: the review runs on the baseline.
3. Run one reviewer in a fresh subagent, passing everything below the line in references/reviewer-brief.md with placeholders filled and paths absolute. If your harness has no subagents, stop and tell the user to run this skill in a fresh session: the context that wrote the change will agree with it. Check the block it returns: it matches the template, every

   file:line

   points at the code it describes in the working tree, and it is at most 400 words. On a miss, send it back once naming what failed; if it still fails, return it with a

   Shape:

   line after

   Dropped:

   .
4. Check the fixes, unless the call carried

   --no-check

   (a caller running its own gate). If the reviewer fixed anything, run the project's typecheck, lint and tests once, taken from the agent instructions, then the package scripts, then CI. Leave fixes in place when a check fails; the next step's owner decides.

Report

Checks: <command> pass | <command> fail: <first failing step> | not run: no fixes | not run: --no-check
Dropped: <paths, or "none">

blocks