code-reviewer

Automate code reviews for local changes and remote pull requests.

1|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/yeeder0520/MySkills --skill code-reviewer-yeeder0520
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/yeeder0520/MySkills/tree/main/code-reviewer
Command: npx skills add https://github.com/yeeder0520/MySkills --skill code-reviewer-yeeder0520

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides and standardizes code reviews for both local development workflows (staged or unstaged changes) and remote Pull Requests, helping teams ensure correctness, maintainability, and adherence to project standards.

Core Features & Use Cases

  • Determine Review Target: automatically direct focus to a remote PR when a PR number or URL is provided, or to local changes when no PR is specified.
  • Preparation & Context: for remote PRs, checkout the PR, run preflight checks, and read the PR description; for local changes, inspect git status and diffs and optionally run preflight.
  • In-Depth Analysis & Feedback: evaluate correctness, maintainability, readability, efficiency, security, edge cases, and testability; provide structured feedback with a clear recommendation.
  • Structured Output: deliver a concise summary, categorized findings (Critical / Improvements / Nitpicks) and a final decision (Approved / Request Changes).
  • Real-world example: review a PR with a complex change set to ensure it integrates cleanly with the main branch and passes CI.

Quick Start

Describe the changes you want reviewed or provide the PR URL or number to begin the remote review.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I automate code reviews for local git changes and remote pull requests?

Automate code reviews for local git changes and remote pull requests by directing the skill to inspect staged diffs or checkout a PR by ID or URL, evaluating correctness, maintainability, and security before providing structured feedback.

What is the best way to review a pull request for correctness and security before merging?

Reviewing a pull request for correctness and security involves checking out the PR, running preflight checks, reading the description, and analyzing the diffs to produce categorized findings and a final decision to approve or request changes.

Can I run a code review on staged changes without a remote pull request?

You can run a code review on staged changes without a remote pull request by inspecting your local git status and diffs, optionally running preflight checks, and analyzing the local modifications for readability and efficiency.

Does the code review process check for maintainability and edge cases in my diffs?

The code review process checks for maintainability and edge cases in your diffs by evaluating correctness, readability, efficiency, security, and testability, returning categorized findings as Critical, Improvements, or Nitpicks.

How do I get structured feedback and a clear decision from a git pull request review?

To get structured feedback and a clear decision from a git pull request review, the skill provides a concise summary, categorizes findings by severity, and outputs a final decision to either approve or request changes.

What are the limitations of automating static analysis for code quality assurance?

Limitations of automating static analysis for code quality assurance include depending on provided PR URLs or local git diffs for context, requiring optional preflight checks to be configured, and standardizing feedback without replacing human judgment.