pr-reviewer

Reviews GitHub pull requests and generates prioritized feedback with a Trello-like board.

2|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/onejaejae/skills --skill pr-reviewer-onejaejae
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-reviewer
Source: https://github.com/onejaejae/skills/tree/main/user-scope-skills/pr-reviewer
Command: npx skills add https://github.com/onejaejae/skills --skill pr-reviewer-onejaejae

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the code review process, ensuring consistency, thoroughness, and constructive feedback, ultimately improving code quality and team collaboration.

Core Features & Use Cases

  • Systematic Review Workflow: Guides users through a structured 4-step review process.
  • Contextual Analysis: Analyzes PR details (title, body, file changes, line counts) and assesses changes based on size and type.
  • Multi-faceted Review: Evaluates code from quality, security, performance, testing, and documentation perspectives.
  • Constructive Feedback Generation: Provides clear, actionable feedback with Pn priority levels, adhering to a friendly and helpful tone.
  • Automated Submission: Can automatically submit review comments and decisions via the GitHub CLI.
  • Use Case: A developer submits a Pull Request. The pr-reviewer skill analyzes the changes, identifies potential issues across various dimensions, and generates a detailed review with specific, prioritized comments for the author to address.

Quick Start

Use the pr-reviewer skill to review the pull request with number 123.

Frequently Asked Questions about pr-reviewer

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

FAQPage Schema
How do I automate GitHub pull request reviews for code quality and security?

Automating GitHub pull request reviews involves analyzing file changes and providing structured feedback on code quality, security, performance, and documentation. This process uses a systematic workflow to assess PR details and generate prioritized, actionable comments for the author.

Can I review local branch diffs instead of a GitHub PR URL?

Yes, you can review local branch diffs. The review process supports both GitHub PR URLs and local branch diffs, allowing you to analyze code changes and assess stability, testing, and documentation without needing a fully published pull request.

Do I need the GitHub CLI installed to submit automated code review comments?

Yes, you need the GitHub CLI installed to submit automated code review comments. The automated submission of review comments and decisions relies on the GitHub CLI to interact with your repository and post the generated feedback directly to the pull request.

What is the best way to provide constructive feedback on a pull request?

The best way to provide constructive feedback on a pull request is through a structured workflow that evaluates code from multiple perspectives. This includes generating clear, actionable insights with priority levels, adhering to a friendly and helpful tone to improve team collaboration.

How does a systematic code review workflow handle different PR sizes?

A systematic code review workflow handles different PR sizes by analyzing PR details like file changes and line counts. It assesses changes based on size and type, ensuring the review remains thorough and contextual whether the pull request is large or small.