skills sourced live from GitHub · all skills listed are free · each skill is provided under its author's license.
home / Coding / Code Review Skill by @mattpocock
The skill is the skills/engineering/code-review folder inside that repository. Copy it into the folder your agent loads skills from; check your agent's documentation for where that is.
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…
Reviews everything since a fixed point, such as a commit, branch, tag or merge-base, along two axes: does the code follow your repository's documented standards, and does it match the issue or spec it came from? It runs both checks with sub-agents and combines the results.
The original SKILL.md is organised into these sections:
Written and maintained by @mattpocock. It is published under the MIT license, which allows reuse with attribution. See the author profile. SkillDirectory does not claim authorship: this page adds our own review and links back to the original, and the skill's text belongs to its author.
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`. ## Process ### 1. Pin the fixed point Whatever the user said is the fixed point (a commit SHA, branch name, tag, `main`, `HEAD~5`, etc.). If they didn't specify one, ask for it. Capture the diff command once: `git diff <fixed-point>...HEAD` (three-dot, so the comparison is against the merge-base). Also note the list of commits via `git log <fixed-point>..HEAD --oneline`. …
Excerpt only, quoted from the author's repository. Open the repository for the complete file.