review

Review staged git diffs for bugs and unhandled error conditions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews staged changes or a branch diff for bugs, missed edge cases, and unhandled error conditions. You do not touch the code. You report findings only.

Core Features & Use Cases

  • Diff inspection examines git changes for logic errors, boundary conditions, and potential failure modes.
  • Context-aware review references the feature spec or documentation to validate that changes align with intended behavior.
  • Non-destructive reporting delivers a structured findings summary without modifying any source files.

Quick Start

Ask Claude to review the current staged changes before commit by saying 'review this'.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review staged changes for bugs and edge cases before committing?

Reviewing staged changes for bugs and edge cases involves reading the git diff and analyzing the modifications for logic errors, boundary conditions, and unhandled error conditions, then outputting a structured findings report without modifying the source code.

What is a non-destructive code review of a branch diff?

A non-destructive code review of a branch diff evaluates git changes for potential failure modes and missed edge cases, reporting findings in a structured summary while ensuring the original source files remain completely unmodified.

Can I validate staged changes against a feature spec during a code review?

Yes, context-aware code review references the feature spec or documentation when available to validate that staged changes align with the intended behavior and surface any discrepancies or unhandled error conditions.

How do I check a pull request for unhandled error conditions?

Checking a pull request for unhandled error conditions requires reading the branch diff via git, inspecting the modifications for logic errors and boundary conditions, and delivering a structured findings report without touching the code.

Does code review of staged changes require modifying the source code?

No, code review of staged changes is a non-destructive process that strictly reports findings. It reads the diff via git and outputs a structured findings summary of bugs and edge cases without modifying any source files.