skills.rest
benrapport
benrapportCOMMUNITY
Explore all skills by this author →
GitHub

review

Analyze git diffs against the base branch to classify actionable items.

Updated Mar 31, 2026
Search Tags:#planning#review#diff-analysis#gstack#scope-drift#actionable-items
One-click install
npx skills add https://github.com/benrapport/Vote-Better --skill review-benrapport
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/benrapport/Vote-Better/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/benrapport/Vote-Better --skill review-benrapport

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR reviews are time-consuming and error-prone. This Skill analyzes diffs against the base branch to surface structural issues and potential gaps that tests may miss.

Core Features & Use Cases

  • Detect scope drift and missing requirements by comparing the branch diff to the PR intent.
  • Extract actionable items and status (CODE | TEST | MIGRATION | CONFIG | DOCS) for quick triage.
  • Provide a plan-ready summary with evidence, rationale, and next steps for the reviewer.

Quick Start

Run /review to start the pre-landing PR review workflow against this branch.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate pre-landing PR reviews to detect scope drift?▼

Automating pre-landing PR reviews involves analyzing a git diff against the base branch to surface structural issues and potential gaps. This process detects scope drift and missing requirements by comparing branch changes to the PR intent.

What is the best way to classify actionable items in a git diff for triage?▼

Classifying actionable items in a git diff involves parsing the changes and categorizing them into CODE, TEST, MIGRATION, CONFIG, or DOCS. This classification provides a status-ready plan for quick triage during PR reviews.

How does diff analysis identify missing requirements that tests may miss?▼

Diff analysis identifies missing requirements by parsing structural changes against the base branch and comparing them to PR intent. It reads TODOS.md for plan alignment when present, surfacing quality gaps across code, tests, docs, and configuration.

Can I use a PR review tool to generate a plan-ready summary with next steps?▼

Yes, you can use a PR review tool to generate a plan-ready summary by analyzing branch diffs. It extracts actionable items, provides evidence and rationale, and outputs next steps formatted for quick reviewer triage.

Do I need a TODOS.md file to perform automated diff analysis for scope drift?▼

No, a TODOS.md file is not required to perform automated diff analysis. The review process parses the diff against the base branch to surface issues, but it reads TODOS.md for plan alignment when the file is present.

Related Skills

Explore More Software Engineering Skills→
bajajvinamrbajajvinamr

review

Analyze PR diffs for SQL safety, trust boundary violations, and side effects.

Community
Advanced
huichenhuichen

review

Analyze branch diffs for structural issues and classify plan items.

Community
Advanced
HenquewlHenquewl
7

finishing-a-development-branch

Verify test suites and finalize git development branches through merge or cleanup.

Community
Advanced
julianobarbosajulianobarbosa
7

reviewing-code

Review code for quality, bugs, security issues, and best practices using Codex.

Community
Advanced