review

Analyze git diff output to surface correctness and security issues in uncommitted changes.

Updated Feb 12, 2026

Search Tags:#security #quality-assurance #code-review #development-workflow #git-diff #review-process

Ready to run

npx skills add https://github.com/obenland/dotfiles --skill review-obenland

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review
Source: https://github.com/obenland/dotfiles/tree/main/claude/.claude/skills/review
Command: npx skills add https://github.com/obenland/dotfiles --skill review-obenland

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review current changes before committing to ensure code quality and safety.

Core Features & Use Cases

Analyzes diffs and staged changes for correctness and security issues.
Checks for common problems (edge cases, security gaps, coding standards, performance concerns) and flags potential risks before commit.
Supports fragile guidance review when present to flag dangerous edits.

Quick Start

Review the current working tree and run a diff-based assessment to produce a verdict before committing.

Frequently Asked Questions about review

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

FAQPage Schema

How do I review uncommitted git changes for security and correctness issues?▼

A pre-commit code review analyzes git diff output to surface correctness and security issues in staged and unstaged changes. It provides a structured workflow that flags edge cases and security gaps, returning a concise verdict with suggested fixes.

What common code issues should I check before committing a git diff?▼

Before committing, check for edge cases, security gaps, coding standard violations, and performance concerns. A pre-commit review evaluates the diff to flag these potential risks and identifies dangerous edits in fragile codebase areas.

Can I run a code review on staged and unstaged changes across multiple files?▼

Yes, you can review staged and unstaged changes across multiple files and projects. The review process requires supporting context such as file statuses and potential fragile areas to accurately evaluate the modifications.

What is the best way to automate a security check on my current working tree?▼

Run a diff-based assessment on your working tree to automate a security check. This evaluates uncommitted changes to identify security gaps and fragile areas, producing a structured verdict with suggested fixes before committing.

Does a pre-commit code review require any specific dependencies or setup?▼

No dependencies are required for this pre-commit code review. It operates by analyzing git diff output and requires supporting context like file statuses and knowledge of potential fragile areas to function effectively.