code-review

Automate pre-commit code reviews with structured feedback and blocking commits.

86|9|Updated Nov 12, 2025
One-click install
npx skills add https://github.com/arpitnath/claude-capsule-kit --skill code-review-arpitnath
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/arpitnath/claude-capsule-kit/tree/main/skills/code-review
Command: npx skills add https://github.com/arpitnath/claude-capsule-kit --skill code-review-arpitnath

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bugs, security issues, and quality problems often slip into code when reviews happen after commits. This Skill enforces mandatory pre-commit reviews to catch issues before they reach version control.

Core Features & Use Cases

  • Mandatory pre-commit review using the code-reviewer agent with structured feedback and an approval workflow.
  • Manual invocation only via /code-review to prevent auto-triggered reviews.
  • Phase-based workflow (Identify changes, Launch reviewer, Analyze feedback, Fix issues, Re-review & approve, Commit) to guide developers through a thorough, repeatable code-quality gate.

Quick Start

Invoke /code-review before you run git commit to start the pre-commit review workflow.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate pre-commit code reviews to catch bugs before committing?▼

Pre-commit code reviews are automated by invoking /code-review before git commit to analyze changed files and return structured feedback identifying CRITICAL issues, WARNINGS, and a final VERDICT. This enforces a mandatory quality gate blocking commits on REQUEST_CHANGES until resolved.

What's the best way to stop security issues and quality problems from slipping into version control?▼

The best way to stop security issues from reaching version control is enforcing a six-phase pre-commit workflow: identify changes, launch reviewer, analyze feedback, fix issues, re-review, and commit. This catches bugs before they are committed rather than reacting after the fact.

Can I use an integrated code-reviewer agent for manual pre-commit checks?▼

Yes, pre-commit checks require an integrated code-reviewer agent to function. The workflow is manually triggered via the /code-review command to prevent auto-triggered reviews, ensuring developers intentionally launch the agent to analyze changed files.

How does the pre-commit review workflow handle blocking commits on critical issues?▼

Pre-commit review workflow handles blocking commits by returning a REQUEST_CHANGES verdict for CRITICAL issues. This halts the git commit process, forcing developers into a fix, re-review, and approve cycle before the commit is allowed.

Does the code-review automation auto-trigger on git commit?▼

No, code-review automation does not auto-trigger on git commit. It operates strictly in manual invocation mode via the /code-review command, allowing developers to explicitly initiate the pre-commit analysis workflow when they are ready.