code-reviewer

Review code diffs and PRs for correctness, security, and maintainability.

3|2|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/JayRHa/AgentSkills --skill code-reviewer-jayrha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/JayRHa/AgentSkills/tree/main/code-reviewer
Command: npx skills add https://github.com/JayRHa/AgentSkills --skill code-reviewer-jayrha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically conducts a structured review of code changes (diffs/PRs) to surface correctness, security, and quality issues, with severity-ranked findings and concrete fixes.

Core Features & Use Cases

  • Structured, diff-scoped reviews focusing on changed code and touched files.
  • Produces actionable findings with file/line references and fix suggestions.
  • Ideal for pre-merge gates, gatekeeping PRs, and self-review of patches.

Quick Start

Paste a diff or describe the changes and ask me to review them for correctness and quality.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I review code diffs for correctness and security before merging?

To review code diffs for correctness and security, you can paste a diff or describe the changes to receive a structured report with severity-ranked issues and concrete fixes. This surfaces bugs across languages by focusing on changed code and touched files.

What is the best way to automate static analysis on a pull request?

Automating static analysis on a pull request involves reviewing changed code to surface bugs and quality issues. This approach produces actionable findings with file and line references, ideal for pre-merge gates and self-review of patches.

Can I use a diff review tool across multiple programming languages?

Yes, you can review diffs across multiple programming languages. The review process applies to changed code and touched files regardless of language, surfacing a structured set of findings with severity-ranked issues and concrete fixes.

Does code review work with staged changes and pre-merge patches?

Code review works with staged changes and pre-merge patches by evaluating correctness, security, and maintainability. It scopes the review to the diff, producing actionable findings with file and line references along with fix suggestions.

What are the limitations of automated diff review for security and quality?

Automated diff review focuses on changed code and touched files within the provided diff. It surfaces severity-ranked findings and concrete fixes, but its scope is limited to the patch context rather than the entire repository architecture.