reviewpr

Coordinate GitHub PR reviews by gathering data, delegating analysis, and posting inline comments.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/thethirdorigin/skills --skill reviewpr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewpr
Source: https://github.com/thethirdorigin/skills/tree/main/plugins/thethirdorigin-skills/skills/reviewpr
Command: npx skills add https://github.com/thethirdorigin/skills --skill reviewpr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires audit.

What problem does it solve?

Deep code review for PRs by orchestrating PR data gathering, delegating analysis to the audit skill, deduplicating existing comments, presenting findings in a severity-grouped table with selectable IDs, and posting user-approved issues as line-specific GitHub comments.

Core Features & Use Cases

  • Gathers PR context via gh CLI
  • Delegates analysis to the audit skill
  • Deduplicates against existing comments
  • Presents findings in a severity-grouped table with selectable IDs
  • Posts user-approved issues as line-specific GitHub comments
  • Use Case: When reviewing complex PRs and needing centralized, audit-backed feedback

Quick Start

Invoke this skill on a PR to run an audit-backed review and post inline comments.

Frequently Asked Questions about reviewpr

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

FAQPage Schema
How do I automate deep PR code review with line-specific GitHub comments?

Automated PR code review with line-specific GitHub comments gathers PR context via gh CLI, delegates analysis to an audit skill, and posts user-approved findings as inline comments. It deduplicates existing comments before posting severity-grouped results.

Do I need gh CLI to run audit-backed findings on a GitHub pull request?

Yes, gh CLI is required to run audit-backed findings on a GitHub pull request. The review process depends on gh CLI for PR context gathering and GitHub API access to post line-specific review comments.

What's the best way to deduplicate existing PR comments before posting new findings?

Deduplicating existing PR comments before posting new findings is handled automatically during the review orchestration. The skill checks current comments against new audit findings and skips redundant issues before posting.

Can I select specific audit findings to post as inline PR comments instead of all of them?

Yes, you can select specific audit findings to post as inline PR comments. The skill presents findings in a severity-grouped table with selectable IDs, allowing you to approve only chosen issues for line-specific GitHub comments.

Does the PR review skill work across different programming languages?

Yes, the PR review skill works across different programming languages. It is applicable to GitHub pull requests across all languages, surfacing findings from the audit and posting results as line-specific comments.

Why are my audit findings showing as a severity-grouped table instead of inline comments?

Audit findings show as a severity-grouped table first to allow user review and selection. You must approve specific findings by selecting their IDs before the skill posts those chosen issues as line-specific GitHub comments.