code-review

Automate code reviews for local diffs and GitHub PRs with artifact reports.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/yandy-r/claude-plugins --skill code-review-yandy-r
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/yandy-r/claude-plugins/tree/main/.cursor-plugin/skills/code-review
Command: npx skills add https://github.com/yandy-r/claude-plugins --skill code-review-yandy-r

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Reduces manual overhead by automating and standardizing code reviews for local changes and GitHub PRs. It ensures consistent quality checks across multiple modes and scales with parallel or team-based workflows when reviewing larger changesets.

Core Features & Use Cases

  • Local Review: perform security, correctness, and quality checks on uncommitted diffs.
  • PR Review: fetch and review full PR head contents with tool-assisted validation.
  • Artifact generation: produce a machine-readable report suitable for downstream fixes and audits.

Quick Start

Run /code-review to begin a local diff-based review and generate a machine-readable artifact.

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 review for uncommitted local diffs?

To automate code review for uncommitted local diffs, execute a local mode review that performs security, correctness, and quality checks directly on your working changes.

Can I review a full GitHub pull request branch with automated checks?

You can review a full GitHub pull request branch by running PR mode, which fetches and analyzes the complete PR head contents with tool-assisted validation for correctness and security.

How does parallel code review work for large changesets?

Parallel code review for large changesets works by executing scalable, team-based analysis across multiple modes, ensuring consistent quality checks without manual overhead.

What is generated when an automated code review finishes?

When an automated code review finishes, it generates a machine-readable artifact suitable for downstream fixes and audits, combining a standardized checklist across correctness, security, and quality.

Do I need any external dependencies to run automated pull request checks?

You do not need external dependencies to run automated pull request checks, as the code review process operates independently to fetch PR head contents and validate correctness, security, and quality.