review-agent

Reviews code diffs and returns prioritized actionable defect findings.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/AarnavBaddam/skills --skill review-agent-aarnavbaddam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-agent
Source: https://github.com/AarnavBaddam/skills/tree/main/.system/review-agent
Command: npx skills add https://github.com/AarnavBaddam/skills --skill review-agent-aarnavbaddam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often miss real defects or get buried in style nitpicks and speculative concerns. This Skill performs a read-only, defect-first review of a code change and returns only concrete, actionable findings the author would likely fix. ## Core Features & Use Cases - Defect-First Review: Inspects the full diff and surrounding code to identify regressions affecting correctness, security, performance, or maintainability. - Base-Branch Comparison: Resolves merge-base against the branch upstream to review the changes that would actually merge, not just a raw diff against the branch tip. - Prioritized Findings: Reports each issue with a P0-P3 severity, file and line reference, and a short explanation, followed by an overall assessment and test gaps. - Use Case: Delegate review of uncommitted changes or a feature-branch diff before merging, and receive a concise list of verified defects instead of noise. ## Quick Start Use the review-agent skill to review my uncommitted changes and return every actionable finding.

Frequently Asked Questions about review-agent

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

FAQPage Schema
How do I review a code diff for actionable bugs?

Inspect the complete diff plus surrounding code, then flag only discrete defects affecting correctness, security, performance, or maintainability that were introduced by the change. Verify each finding against tests and call sites before reporting it with a severity priority.

How to review changes against a base branch correctly?

Resolve the comparison ref to the branch's upstream when it exists and is ahead, then run git merge-base HEAD <ref> and inspect git diff from that merge-base. This reviews the changes that would actually merge rather than diffing against the branch tip.

Can this review agent modify files or post comments?

No. The review is strictly read-only: it does not modify files, create commits, push branches, post review comments, or delegate to another agent. It only inspects the target and returns findings.

What kinds of issues does a defect-first code review skip?

It skips speculative concerns, pre-existing problems, intentional behavior changes, and style nits that do not obscure the code. An issue is flagged only when it is demonstrable from the code and the author would probably fix it.

What happens when a code review finds no defects?

The review reports "No findings." rather than inventing issues to fill the result. It still adds a brief overall assessment noting material test gaps or residual risks.