Works with
Packaged from the source skill for Claude, Codex and 4 more.
About this skill
This code-review workflow separates two questions: whether a change follows the repository's documented conventions and whether it implements the intended specification. It anchors both assessments to the same Git comparison and presents their findings side by side.
Use this skill when
- A branch needs review before it becomes a pull request.
- You want to compare work since a commit, tag or merge base.
- A change appears tidy but may miss requirements, or meets the brief while breaking local conventions.
What it can do
- Validate a fixed Git reference and identify the commits and diff under review.
- Find repository standards and a supplied or discoverable specification.
- Review conventions separately from missing, extra or incorrectly implemented requirements.
- Label code-smell heuristics as judgment calls rather than automatic violations.
Typical workflows
- Supply a resolvable base reference and confirm the comparison contains changes.
- Provide the issue or local specification and identify the repository's standards files.
- Run standards and specification reviews in fresh parallel contexts when the host supports them.
- Read the two reports separately, with quoted evidence and a finding count for each axis.
Inputs and output
Needs a Git repository, a base reference and the available standards and requirements. The result has separate Standards and Spec reports. Issue fetching depends on the workspace's tracker configuration; a local specification can provide the requirements directly.
Limitations
With no specification, the requirements axis is explicitly skipped. Parallel review requires sub-agent support. The workflow is a qualitative review and does not replace executing the project's tests, static analysis or a dedicated security assessment.
What is inside the skill
Section headings from the original SKILL.md (about 1,021 words of instructions). Read the full text in the source repository before installing.
- 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
Bundled files
agents/openai.yamlLICENSE
Example prompts
- Review my feature branch against main, checking CONTRIBUTING.md separately from docs/specs/invoice-export.md.
- Compare HEAD with release-2.4 and report standards violations independently from requirements missing in issue 182.
- Review the last five commits with our coding standards; no written specification exists, so mark the specification axis unavailable.
How to install Code Review
Claude Packaged
- Download the Claude package from the skill page. The ZIP contains one folder named after the skill, with SKILL.md and any bundled reference files.
- For Claude Code, unpack the folder into ~/.claude/skills/ to use it in every project, or into .claude/skills/ inside a repository to share it with your team.
- For Claude apps, upload the ZIP in the Skills section of the capabilities settings.
- Start a new session and describe the task in your own words. Claude picks the skill when the request matches its description.
Codex Packaged
- Download the Codex package. The ZIP contains one folder named after the skill, with SKILL.md and bundled resources.
- Unpack the complete folder into .agents/skills/ inside your repository, or into ~/.agents/skills/ for personal use. Preserve its relative reference-file paths.
- Start a new Codex session and invoke the skill by name or with $skill-name, or describe a matching task.
- AGENTS.md is separate project guidance. The ZIP does not generate or modify that file.
GPT Packaged
- Download the GPT package from the skill page.
- Create or edit a custom GPT (or a ChatGPT project) and paste the contents of SKILL.md into the instructions field.
- Upload the bundled reference files as knowledge so the GPT can consult them.
- Test with one of the example prompts from the skill page and adjust the instructions if your use case differs.
Gemini Packaged
- Download the Gemini package from the skill page.
- For a project, unpack the complete folder into .gemini/skills/ or .agents/skills/. For personal use, use ~/.gemini/skills/ or ~/.agents/skills/.
- Run /skills reload in Gemini CLI, then /skills list to check discovery. There is no need to paste the skill into GEMINI.md.
- Test a matching task and verify the referenced tools and files are available.
Cursor Packaged
- Download the Cursor package from the skill page.
- Unpack the complete skill folder into .cursor/skills/ or .agents/skills/ in your project. For personal local use, ~/.cursor/skills/ and ~/.agents/skills/ are also supported.
- Start a new Cursor session. Type / in Agent chat and select the skill name, or describe a matching task.
- Commit the skill folder and resources for team use. Personal local skills are not automatically available to remote agents or automation runs.
OpenCode Packaged
- Download the OpenCode package from the skill page.
- Unpack the complete folder into .opencode/skills/ in your project, or ~/.config/opencode/skills/ for personal use. OpenCode also supports .agents/skills/ and .claude/skills/ compatibility locations.
- Keep supporting files at their original relative paths. AGENTS.md is separate project-wide guidance and is not generated by this ZIP.
- Start OpenCode in the project and test a matching task with the model and permissions you use.
Permissions & security
Inspect the source, license and declared permissions before use. Read the scripts before running them. Review method
Code Review FAQ
What does the Code Review skill do?
Review a Git diff against repository standards and the originating specification in two separate assessments, keeping style and requirement findings distinct.
Which AI agents can use Code Review?
Packages for Claude, Codex and 4 more are built from the same source instructions.
How do I install Code Review in Claude?
Download the Claude package from the skill page. The ZIP contains one folder named after the skill, with SKILL.md and any bundled reference files. For Claude Code, unpack the folder into ~/.claude/skills/ to use it in every project, or into .claude/skills/ inside a repository to share it with your team.
Who made Code Review and what is the license?
Code Review is published by Matt Pocock under the MIT license. The source is https://github.com/mattpocock/skills/tree/main/skills/engineering/code-review. The catalog keeps the original attribution.
What permissions does Code Review need?
Declared permissions: read project files, write generated skill files. Risk level: low. Check the scripts in the source before running them.