review-code

Reviews pending code changes against repo conventions and produces a prioritized findings report.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/hpark0011/mirror --skill review-code-hpark0011
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-code
Source: https://github.com/hpark0011/mirror/tree/main/.agents/skills/review-code
Command: npx skills add https://github.com/hpark0011/mirror --skill review-code-hpark0011

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing diffs by hand is slow and inconsistent, and generic AI reviews often miss repo-specific conventions or invent noise. This Skill runs a structured, multi-phase code review of pending changes against the repository's own rules (AGENTS.md, .claude/rules/) and returns a prioritized, deduplicated findings report. ## Core Features & Use Cases - Scoped diff ingestion: Review a branch, staged changes, a file path, or a custom base ref, with worktree and untracked-file pre-flight checks. - Specialist reviewer routing: Dispatches parallel reviewer agents for correctness, conventions, tests, maintainability, concurrency, security, performance, and more based on the diff's risk surface. - Normalization and confidence gating: Deduplicates findings by fingerprint, boosts cross-reviewer agreement, filters low-confidence noise, and separates pre-existing issues from new ones. - Actionable output: Produces a P0–P3 prioritized markdown report, files issue tickets for blockers, and offers safe auto-fixes with a build/lint exit gate. - Use Case: Before merging a branch that fixes a chat streaming race condition, run the skill to catch a missed lock release on cancellation, get it filed as a ticket, and verify the fix with a green build. ## Quick Start Ask the AI to review my current branch changes against main and report any critical issues before I merge.

Frequently Asked Questions about review-code

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

FAQPage Schema
How do I review code changes before committing with AI?▼

Run the review-code skill with a scope argument such as a branch name, --staged, or a file path. It computes the diff, loads matching repo rules, dispatches specialist reviewers, and returns a prioritized P0–P3 findings report with file:line anchors.

What is the difference between review-code and review-pr?▼

review-code analyzes local pending changes (diffs, branches, staged files) against repo conventions. review-pr fetches and processes GitHub PR review comments instead, and security-review focuses on threat modeling rather than general code quality.

Can the skill automatically fix the issues it finds?▼

Yes, but only findings classified as safe_auto with owner review-fixer are applied automatically, and only after user confirmation. Gated fixes need per-item approval, and the skill re-runs build and lint until green before exiting.

Does it work without a .claude/rules directory?▼

Yes. If .claude/rules/ is missing, it falls back to whatever convention docs the repo uses, such as AGENTS.md, CLAUDE.md, CONTRIBUTING.md, or docs/conventions/. Rule files are matched to the diff by topic based on filename.

Why does the review report show a pre-existing issues section?▼

Findings flagged as pre_existing were not introduced by the current diff; the change merely touched that area. They are surfaced in a separate section for awareness and do not count toward the merge verdict.