review-code

Review code diffs across security, reliability, maintainability, and generalist axes with parallel reviewer personas.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often miss defects because a single reviewer cannot simultaneously watch for security holes, reliability failures, maintainability drift, and general quality issues. This Skill coordinates four specialized review personas in parallel, then aggregates, deduplicates, filters, and triages their findings into a single verdict. ## Core Features & Use Cases - Four-axis parallel review: Dispatches security, reliability, maintainability, and senior-generalist reviewer personas against the same diff, with support for named axis subsets. - Aggregation and triage pipeline: Deduplicates overlapping findings, filters by confidence and priority, assigns REVIEW-NNN ids, and asks the user to classify each blocking finding as Fix or Accept. - Accepted Review Exceptions registry: Records human-approved waivers as AR entries in AGENTS.md so accepted risks are remembered and automatically downgraded on later reviews. - Use Case: Before merging a feature branch, run the review against git diff main...HEAD to receive prioritized findings with locations, confidence levels, and a Stage Status of pass, needs-decision, or changes-required. ## Quick Start Review the changes on my current branch against main and report any blocking security or reliability findings.

Frequently Asked Questions about review-code

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

FAQPage Schema
How do I review a git diff for security and reliability issues?▼

Run the review against your branch diff, which defaults to git diff main...HEAD including uncommitted changes. Four reviewer personas inspect the diff in parallel across security, reliability, maintainability, and general quality axes, and findings are aggregated into a prioritized report.

How do I review only part of a codebase or a single file?▼

Point the review at a specific file, a pull request base branch, or the whole tree to override the default branch diff scope. For diffs over roughly 2000 changed lines, the review automatically processes one file at a time with a fresh set of reviewers per file.

Can I run only some review axes instead of all four?▼

Yes, you can name any subset of the four axes, such as maintainability plus senior-generalist for a lighter review. The final output states which axes ran so a clean verdict is not mistaken for full coverage.

What happens when a review finds a blocking issue I want to accept?▼

During triage you classify each CRITICAL or HIGH finding as Fix or Accept. Accepted findings are recorded as AR entries in the nearest AGENTS.md file, and future reviews automatically downgrade matching findings instead of reporting them again.

Why does the review report low-confidence findings instead of hiding them?▼

Reviewers report everything they can concretely name with a confidence tag, and filtering happens during aggregation rather than in the reviewer. Low-confidence non-blocking findings appear as one-line notes so uncertain observations reach you instead of being silently discarded.