review-change
The implementer makes it work, this skill makes it good, in a context that did not write it. The reviewer's default output is a fix; it reports only what it may not fix. It judges standards and fit with the rest of the codebase, not the spec, and passes on a bug only as a question.
Arguments: an optional fixed point, an optional --no-check, then optional standards paths.
Steps
-
Pin the diff. The fixed point defaults to the merge-base of
HEADand the default branch;HEADmeans uncommitted work only. Resolve it withgit 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>plusgit 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. -
Find the standards, all of them, in precedence order: paths passed as arguments,
.agents/coding-standards.md,CODING_STANDARDS.md,CONTRIBUTING.mdand 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 everyAGENTS.mdandCLAUDE.mdat the root or in a touched directory. Find the glossary too,spec/glossary.md(elseGLOSSARY.mdorCONTEXT.md), which the reviewer judges a Drifted term against. No standards at all is normal: the review runs on the baseline.