code-review
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
Install
git clone https://github.com/mattpocock/skills /tmp/skills && ln -s /tmp/skills/skills/engineering/code-review ~/.claude/skills/code-reviewFrom README
Process Pin the fixed point Whatever the user said is the fixed point (a commit SHA, branch name, tag, main, HEAD5, etc.). If they didn't specify one, ask for it. Capture the diff command once: git diff ...HEAD (three-dot, so the comparison is against the merge-base). Also note the list of commits via git log ..HEAD --oneline. Before going further, confirm the fixed point resolves (git rev-parse ) and the diff is non-empty. A bad ref or empty diff should fail here, not inside two parallel sub-agents. Identify the spec source Look for the originating spec, in this order: Issue references in the commit messages (#123, Closes #45, GitLab !67, etc.), fetched via the workflow in docs/agents/issue-tracker.md. A path the user passed as an argument. A spec file under docs/, specs/, or .scratch/ matching the branch name or feature. If nothing is found, ask the user where the spec is. If they say there isn't one, the Spec sub-agent will skip and report "no spec available".