review

Reviews git diffs for bugs, security issues, debug artifacts, and style problems before commit.

Updated Jul 27, 2025
One-click install
npx skills add https://github.com/TheCactusBlue/nixfiles --skill review-thecactusblue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/TheCactusBlue/nixfiles/tree/main/.claude/skills/review
Command: npx skills add https://github.com/TheCactusBlue/nixfiles --skill review-thecactusblue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams catch bugs, security issues, debug artifacts, and style problems before commits.

Core Features & Use Cases

  • Automated diff analysis to detect defects and style violations in staged or unstaged changes.
  • Security and artifact checks to surface secrets, unsafe patterns, and leftover debugging code.
  • Use Case: Prepare a PR by scanning diffs for TODOs, console logs, and insecure patterns, then present findings for review.

Quick Start

Run the pre-commit self-review on your current changes. Start with git diff --staged to capture staged changes; if nothing is staged, fall back to git diff for unstaged changes; if both are empty, the tool will report nothing to review. If a CLAUDE.md exists at the project root, read it for project-specific rules before proceeding. Then review findings and decide on fixes or actions.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review staged git diffs for security issues and style violations before committing?

Pre-commit self-review scans staged or unstaged git diffs to identify security issues, bugs, debug artifacts, and style violations. It parses local changes and presents clear findings for you to review without auto-fixing.

Can I check my unstaged code changes for leftover debug artifacts and TODOs before preparing a pull request?

Yes, diff analysis detects leftover debugging code, console logs, TODOs, and insecure patterns in local changes. If nothing is staged, it falls back to unstaged changes to help you prepare clean pull requests.

Does the pre-commit code review read project-specific lint and style rules?

Yes, if a CLAUDE.md file exists at the project root, the review reads it for project-specific rules before proceeding. This ensures the diff analysis respects your established code quality guidelines.

What happens if there are no staged or unstaged changes when running a diff analysis?

If both staged and unstaged diffs are empty, the review tool reports nothing to review. It requires local changes to parse for defects, security issues, and style problems.

Will the pre-commit review automatically fix the bugs and security issues it finds in my diff?

No, the review presents clear findings without auto-fixing. It surfaces secrets, unsafe patterns, and style problems so you can review the findings and decide on fixes or actions yourself.

What is the best way to perform a code audit on incremental commits?

Run a pre-commit self-review on your current local changes. Use git diff --staged to capture staged changes for incremental commits, and the tool will parse the diff to surface defects and style violations for your audit.