review-code

Reviews a code diff through one focus brief and writes a structured severity-tiered review file.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/mikestopcontinues/agent-skills --skill review-code-mikestopcontinues
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-code
Source: https://github.com/mikestopcontinues/agent-skills/tree/main/claude/skills/review-code
Command: npx skills add https://github.com/mikestopcontinues/agent-skills --skill review-code-mikestopcontinues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Code reviews often suffer from scope creep, inconsistent formats, and reviewers flagging issues outside their mandate. This Skill enforces single-focus, diff-only code review with a fixed output template so findings are consistent, parseable, and routed correctly. ## Core Features & Use Cases - Single-focus review: Resolves one focus brief (accuracy, architecture, or dx), adopts the named persona, and reviews exactly one diff without fanning out to subagents. - Diff resolution: Accepts a .diff/.patch file, source file, or directory and derives the change via git diff against a configurable base ref, with an explicit empty-diff fallback. - Standardized output: Writes one rNN-{focus}.md file with fixed Blockers/Majors/Minors/Nits sections so downstream triage tooling can parse every review uniformly. - Use Case: An orchestrator like validate-code dispatches three parallel reviews of a pull request diff — one accuracy, one architecture, one dx — and each returns a consistently formatted findings file for triage-feedback to merge. ## Quick Start Ask the agent to review the current branch diff against master using the architecture focus and write the findings file to the review directory.

Frequently Asked Questions about review-code

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a focused code review on a git diff?▼

Provide the focus name (accuracy, architecture, or dx), the artifact path, a target filename, and an iteration number. The skill resolves the artifact to a diff using git diff against the base ref, applies the focus brief, and writes one rNN-{focus}.md findings file.

What review focuses are available for code review?▼

The baseline focuses with authored briefs are accuracy (spec and test coverage), architecture (module boundaries and coupling), and dx (developer-facing ergonomics). Contextual focuses like security, performance, and compatibility require authoring a brief first.

Can the reviewer edit code or spawn subagents during review?▼

No. The reviewer runs with Read, Glob, Grep, and Bash only, where Bash is restricted to git diff and mktemp. It never spawns subagents, never edits the tree, and its only write is the single review findings file.

What happens when there is no diff to review?▼

If the artifact is unchanged versus the base ref, the skill writes a review file whose summary states there is no diff to review and marks all four severity sections as (none), rather than inventing findings.

Why are findings limited to a single focus per review?▼

Single-focus scope keeps reviews deep and non-overlapping; issues outside the focus belong to sibling reviewers. Cross-reviewer synthesis and deduplication is handled downstream by the triage-feedback skill, not by individual reviewers.