code-review

Identify and report code quality, security, and maintainability issues in diffs.

38.5k|3.5k|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/Yeachan-Heo/oh-my-claudecode --skill code-review-yeachan-heo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/Yeachan-Heo/oh-my-claudecode/tree/main/skills/code-review
Command: npx skills add https://github.com/Yeachan-Heo/oh-my-claudecode --skill code-review-yeachan-heo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams systematically identify and communicate code quality, security, and maintainability issues in code changes.

Core Features & Use Cases

  • Automated review of diffs from git diffs or pull requests to identify changed files and potential issues.
  • Severity-based reporting with precise file:line locations and actionable recommendations.
  • PR workflow support with structured feedback ready for review and remediation.
  • Use Case: Before merging a risky feature, run this skill on the PR to surface critical security gaps and maintainability concerns.

Quick Start

Trigger the code-review skill on the current branch or a PR diff to generate a comprehensive report.

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 find security vulnerabilities?

You can review feature branches by running the skill on a git diff or pull request to systematically surface code quality, security, and maintainability issues before merging.

What is severity-based reporting in static analysis for code changes?

Severity-based reporting in static analysis categorizes identified code quality and security issues by impact level, providing precise file:line locations and concrete remediation examples to guide merges.

Can I use automated code review on any repository branch or diff?

Yes, automated code review applies to pull requests, feature branches, or diffs in any repository, identifying changed files and potential issues to deliver actionable feedback for merge decisions.

How do I get actionable feedback on maintainability issues before merging a risky feature?

To get actionable feedback on maintainability issues before merging, run a code review on the PR diff to surface critical gaps and outline concerns by severity with concrete fix examples.

Does static analysis for code review work without external dependencies or modules?

Yes, static analysis for code review operates without external dependencies or component modules, systematically identifying and communicating code quality and security issues directly from repository diffs.