code-reviewcommit 7739eaeSKILL.md · Code Review
Two-Axis Code Review
Reviews changes since a fixed point on two axes, the repo's coding standards and the originating spec, using parallel sub-agents.
npx skills add mattpocock/skills --skill code-reviewCommand selected. Copy it manually.
- Permissions
- read-repo
- write-files
- shell
- network
- Compatible with
- Claude Code, Codex, Copilot, Gemini CLI
- GitHub
- 308.7k
- Source
- Community · Matt Pocock
- Status
- Scan passed
- License
- MIT
- Category
- Code Review
Core rule
Report the Standards and Spec findings separately and never merge or rerank them across axes.
Execution Phases
Phase 01Pin the fixed point
Confirm the commit, branch or tag resolves and the diff is non-empty, then capture the git diff and git log commands.
Phase 02Identify the spec
Look for issue references in commits, a path the user passed, or a spec file under docs/ or specs/, and ask the user if none is found.
Phase 03Gather the standards
Find every file that documents coding standards and add a baseline of Fowler code smells; documented repo standards override the baseline.
Phase 04Spawn both sub-agents
Launch the Standards and Spec sub-agents together, each with a fresh context and a report under 400 words.
Phase 05Aggregate the reports
Present the results under Standards and Spec headings and end with one line giving the count and worst issue per axis.
Permissions (summarised from SKILL.md)
| Capability | Needed | Details |
|---|---|---|
| File writes | Not required | Produces a review report only and does not change code. |
| Command execution | Limited | Runs git rev-parse, git diff and git log to get the changes and commit list. |
| Network outbound | Limited | Only to fetch issues referenced in commits, via the workflow in the issue tracker doc. |
SKILL.md frontmatter (YAML)
---
name: code-review
description: "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\"."
---