code-review

Automate code reviews for security, quality, and maintainability issues.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/suhwan/claude-registry --skill code-review-suhwan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/suhwan/claude-registry/tree/main/skills/quality/code-review
Command: npx skills add https://github.com/suhwan/claude-registry --skill code-review-suhwan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates and standardizes code quality reviews, helping teams identify security issues, maintainability concerns, and performance problems before merges.

Core Features & Use Cases

  • Automated change analysis using git diff to surface relevant file changes.
  • Severity-based reporting with clear remediation steps for security, quality, and performance issues.
  • Pre-merge validation and post-merge audits to ensure code health over time.

Quick Start

Ask the agent to run a code review on the latest pull request.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate code reviews for pull requests to catch security and performance issues?

Automate code reviews by running an analysis on git diff changes to identify security, performance, and maintainability issues. The review synthesizes findings into a markdown report with file paths, line references, and concrete remediation recommendations for pre-merge validation.

What is the best way to perform a post-merge code audit for maintainability?

Post-merge code audits use automated static analysis to evaluate maintainability and quality across software projects. The process generates a markdown-style report detailing file paths and severity-based remediation steps to ensure long-term code health.

Can I use automated static analysis for pre-merge validation on major feature changes?

Automated static analysis supports pre-merge validation by analyzing git diff for major feature changes. It surfaces security vulnerabilities and quality concerns, providing clear remediation steps before the code is merged into the main project.

How do I generate a code review report with specific file paths and line references?

Generate a code review report by running an analysis on your code changes, which synthesizes findings into a markdown format. The report includes specific file paths, line references, and severity-based recommendations for resolving identified issues.

Does automated code review work without configuring external dependencies?

Automated code review works without external dependencies, analyzing changes directly to identify security and maintainability issues. It operates independently to produce markdown reports with actionable remediation recommendations.

Why should I use severity-based reporting for code quality and security issues?

Severity-based reporting prioritizes code quality and security issues by impact, helping teams address critical vulnerabilities before minor maintainability concerns. This approach ensures clear remediation steps are provided for each identified issue in the markdown report.