review-pr

Review pull request diffs for correctness, readability, performance, and security.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/seetaram-codebase/plugins-registry --skill review-pr-seetaram-codebase
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/seetaram-codebase/plugins-registry/tree/main/code-review-plugin/skills/review-pr
Command: npx skills add https://github.com/seetaram-codebase/plugins-registry --skill review-pr-seetaram-codebase

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Streamlines the code review process, providing a structured methodology for evaluating pull requests.

Core Features & Use Cases

  • Structured Review Process: Guides through understanding context, systematic diff reading, criteria evaluation, and quality gate checks.
  • Customizable Feedback: Offers formats for critical issues, suggestions, and positive observations.
  • Use Case: Before merging a pull request, run the review-pr skill to ensure the code meets quality standards.

Quick Start

Use the review-pr skill to initiate a structured code review on the current pull request.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I do a structured code review on a GitHub pull request?

A structured code review on a GitHub pull request requires analyzing diff changes and evaluating correctness, readability, performance, and security. This process guides you through understanding context, systematic diff reading, and quality gate checks before merging.

What should I look for when reviewing pull request diffs?

When reviewing pull request diffs, you should evaluate code correctness, readability, performance, and security. A structured review process helps handle various codebase scenarios by systematically reading diffs and checking quality gates.

Can I customize the feedback format when reviewing a pull request?

Yes, you can customize pull request feedback by using formats for critical issues, suggestions, and positive observations. This ensures structured feedback covers both necessary fixes and acknowledges good practices.

Does this code review process work for any version control system?

The code review process is designed for version control systems, especially GitHub. It requires analyzing diff changes and handling various codebase scenarios to ensure thorough evaluation before merging.

How do I ensure my code meets quality standards before merging a pull request?

To ensure code meets quality standards before merging, run a structured review on the pull request. This evaluates correctness, readability, performance, and security through systematic diff reading and quality gate checks.