pr-reviewer

Reviews pull requests for correctness, security, performance, architecture, and documentation gaps.

31|2|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/shaharia-lab/agento --skill pr-reviewer-shaharia-lab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-reviewer
Source: https://github.com/shaharia-lab/agento/tree/main/.claude/skills/pr-reviewer
Command: npx skills add https://github.com/shaharia-lab/agento --skill pr-reviewer-shaharia-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Reviewing pull requests thoroughly is time-consuming and inconsistent — reviewers often miss security issues, performance regressions, or cross-platform bugs while nit-picking trivial style details. This Skill performs a structured, senior-engineer-level review across eleven dimensions so real problems get caught before merge. ## Core Features & Use Cases - Multi-Dimensional Review: Checks correctness, code quality, security, performance, architecture, UI/UX, cross-platform compatibility, observability, dependencies, testing, and documentation. - Severity-Ranked Findings: Classifies every issue as MUST FIX, SHOULD FIX, CONSIDER, or QUESTION with file locations, code snippets, and concrete fix suggestions. - Existing Feedback Awareness: Reads prior PR comments and reviews via the GitHub CLI to avoid repeating feedback and to track unresolved threads. - Use Case: Before merging a feature branch, run the reviewer against PR #42 to receive a structured report with a risk level, findings table, documentation checklist, and an APPROVE / REQUEST CHANGES verdict. ## Quick Start Ask the assistant to review pull request 42 or review the current branch against main using the pr-reviewer skill.

Frequently Asked Questions about pr-reviewer

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

FAQPage Schema
How do I review a pull request with an AI assistant?

Provide a PR number, branch name, or ask to review the current branch against main. The reviewer fetches the diff with git or the GitHub CLI, reads every changed file in full, and returns severity-ranked findings with fix suggestions.

What does an automated PR code review check for?

It checks correctness, code quality, security, performance, architecture, UI/UX, cross-platform compatibility, observability, dependencies, testing, and documentation. Each finding includes the file location, code snippet, issue explanation, and a suggested fix.

Does the PR reviewer work with GitHub CLI?

Yes, it uses the gh CLI to fetch PR metadata, diffs, comments, and existing reviews when given a PR number. For branch-based reviews it falls back to git log and git diff commands against main.

Can the reviewer avoid repeating existing PR feedback?

Yes, it reads existing PR comments and reviews before reporting findings. It notes which feedback is resolved or still open and skips issues already raised by other reviewers.

When should I not use an automated PR reviewer?

Avoid relying on it as the sole gate for highly domain-specific logic, legal compliance, or business-rule validation that requires human context. It complements human review but cannot judge product intent or organizational constraints.