code-review

Analyze uncommitted diffs for security and quality issues.

2|2|Updated Mar 21, 2025
One-click install
npx skills add https://github.com/MeshJS/governance --skill code-review-meshjs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/MeshJS/governance/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/MeshJS/governance --skill code-review-meshjs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Security and quality review of uncommitted changes to prevent leakage of secrets, introduction of vulnerabilities, and violations of best practices before committing.

Core Features & Use Cases

  • Automated analysis of diffs to detect secrets, insecure patterns, and code smells.
  • Severity-based grouping with actionable remediation guidance.
  • Suitable for pre-commit workflows, handling both staged and unstaged changes across codebases.

Quick Start

Run the code-review command to scan your current working tree for issues before committing.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I check uncommitted git diff for hardcoded secrets before committing?

A pre-commit code review analyzes your staged and unstaged git diffs to detect hardcoded secrets, categorizes them by severity, and outputs a concise summary with actionable remediation steps.

How do I scan uncommitted changes for insecure patterns and code smells?

Scanning uncommitted changes for insecure patterns and code smells involves automated static analysis of your working tree, which flags violations of best practices and groups them by severity before you commit.

Can I use static analysis to catch security issues in staged and unstaged diffs?

Yes, static analysis can be applied to pre-commit workflows to catch security issues in both staged and unstaged diffs, preventing the introduction of vulnerabilities and hardcoded secrets into the codebase.

What is the best way to automate security and quality review in a pre-commit workflow?

The best way to automate security and quality review in a pre-commit workflow is to run a code review command that analyzes uncommitted changes, categorizes issues by severity, and provides concise remediation guidance.

Does code review for uncommitted changes require external dependencies or components?

No, code review for uncommitted changes requires no external dependencies or components to function, allowing you to directly analyze your working tree for security and quality issues across codebases.