pre-commit-review

Analyze staged and unstaged code changes for security, performance, and quality issues.

1|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/ichuan/skills --skill pre-commit-review-ichuan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pre-commit-review
Source: https://github.com/ichuan/skills/tree/main/skills/pre-commit-review
Command: npx skills add https://github.com/ichuan/skills --skill pre-commit-review-ichuan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill performs a comprehensive pre-commit code review of uncommitted changes to identify security vulnerabilities, bugs, performance issues, and code quality concerns before you commit.

Core Features & Use Cases

  • Pre-commit validation: Scan staged and unstaged changes to catch issues before they enter the repository.
  • 🟡 Severity-based feedback: Classifies findings as 🔴 Critical, 🟡 Warning, or 🔵 Info with actionable remediation guidance.
  • Comprehensive Checklist: Aligns with standard checks for security, performance, quality, and error handling; includes guidance from the references.
  • Actionable Solutions: Provides concrete fixes and improvement suggestions for each issue to streamline remediation.
  • Use Case: Ideal for ensuring code quality in feature branches or before pull requests, preventing regressions.

Quick Start

Run the pre-commit-review skill to analyze your current staged and unstaged changes; review the results and apply suggested fixes before committing.

Frequently Asked Questions about pre-commit-review

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

FAQPage Schema
How do I run a pre-commit code review on my staged and unstaged git changes?

A pre-commit code review scans uncommitted changes to catch security vulnerabilities, bugs, performance issues, and code quality concerns before they enter the repository. It applies to edits across languages and repository layouts, using a comprehensive checklist to ensure code quality.

How does severity-based classification work for pre-commit code review findings?

Severity-based feedback classifies pre-commit review findings as Critical, Warning, or Info. This mechanism helps prioritize remediation by highlighting severe security or performance issues first, accompanied by actionable improvement suggestions for each identified problem.

Can I review code quality across different programming languages before committing?

Yes, pre-commit review applies to changes across languages and repository layouts. It analyzes both staged and unstaged edits for comprehensive validation, checking security, performance, quality, and error handling using a standard checklist.

What is the best way to prevent regressions in feature branches before a pull request?

The best way to prevent regressions is to perform a pre-commit code review on uncommitted changes. This validates security, performance, and quality concerns using a comprehensive checklist, providing actionable remediation guidance before committing to feature branches.

Does pre-commit validation require specific dependencies or tools to analyze uncommitted changes?

Pre-commit validation requires no specific dependencies to analyze uncommitted changes. It works directly on staged and unstaged edits across languages and repository layouts to identify security, performance, and quality concerns without external tool requirements.