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".
Target: Software development & testing. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- Process
- 1. Pin the fixed point
- 2. Identify the spec source
- 3. Identify the standards sources
- 4. Spawn both sub-agents in parallel
- 5. Aggregate
- Why two axes
Two-axis review of the diff between HEAD and a fixed point the user supplies: Standards: does the code conform to this repo's documented coding standards? Spec: does the code faithfully implement the originating issue / spec? Both axes run as parallel sub-agents so they don't pollute each other's context, then this skill aggregates their findings. Start every sub-agent with a fresh context window. The issue tracker should have been provided to you. If not, tell the user to run /setup-matt-pocock-skills. 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. Look for the originating spec, in this order: 1. Issue references in the commit messages (#123, Closes #45, GitLab !67, etc.), fetched via the workflow in the tracker doc. 2. A path the user passed as an argument.
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- mattpocock/skills
- Source file
- skills/engineering/code-review/SKILL.md
- Fixed revision
- 4ae2317ddb22b046e26455e4f9c9b3aaaf62212d
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: Matt Pocock Skills · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-10T18:01:04.561Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.