| name | change-review |
| description | Review a branch, pull request, commit range, or working-tree diff on two axes: repository standards and the originating requirements. Use for explicit code or PR review, independent pre-merge quality gates, and checking an implementation against its specification. Do not use when there is no change set to inspect or the task is only to implement a known fix. |
Change Review
This skill is the two-axis review (standards and specification). For a fast bug-focused pass over the working diff, the bundled /code-review command is the lighter option; use this skill when the change must also be checked against its stated requirements.
Review the exact change against two independent questions: whether it is built correctly and whether it builds the requested thing.
Read references/evidence.md when calibrating scope, finding usefulness, or severity. If delegation is explicitly authorized, apply delegate-work and assign only distinct review axes such as correctness, security, external compatibility, or rendered interface quality; keep synthesis and deduplication in the main session.
Respect the Review Contract
- Treat a review-only request as read-only. Do not modify code, resolve findings, or change repository state.
- When the user explicitly requests review and fixes, complete the evidence-based review first, then correct supported findings and verify the result.
- Review only the requested diff and directly affected behavior. Do not turn the review into a general codebase audit.
- Preserve the distinction between repository standards and product requirements.
Pin the Review Scope
Resolve and verify the fixed point before reviewing:
- the merge base, branch, commit, tag, or working-tree state;
- committed, staged, unstaged, and untracked changes in scope;
- generated, vendored, lock, schema, and migration files affected by the change.
Fail clearly on an invalid base or empty diff. Do not silently substitute a different comparison.
