pr-reviewer

Collect GitHub PR data and generate structured review files with two-stage approval.

46|8|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/SpillwaveSolutions/code_agent_context_hooks --skill pr-reviewer-spillwavesolutions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-reviewer
Source: https://github.com/SpillwaveSolutions/code_agent_context_hooks/tree/main/.opencode/skill/pr-reviewer
Command: npx skills add https://github.com/SpillwaveSolutions/code_agent_context_hooks --skill pr-reviewer-spillwavesolutions

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

PR reviewers and teams spend significant time gathering PR metadata, diffs, comments, and related issues, then manually producing structured review documents and navigating a two-stage approval workflow. This Skill automates PR data collection, organizes a review workspace, analyzes changes against industry-standard criteria, and generates internal and public review artifacts with an optional inline-comment workflow.

Core Features & Use Cases

  • Automated Data Collection: Fetches PR metadata, diffs, comments, commits, and related issues via GitHub CLI
  • Systematic Analysis: Applies a comprehensive quality checklist against the PR changes
  • Structured Review Files: Generates internal review, clean public review, and inline comment templates
  • Two-Stage Approval: Nothing posts to GitHub until explicit approval
  • Inline Comments: Optionally adds code-specific feedback directly to the PR
  • Ticket Tracking: Extracts and links JIRA/GitHub issue references
  • Templates & Workflow: Provides professional templates and commands to streamline posting

Quick Start

Use this skill to fetch a PR, analyze it, and generate review artifacts:

  • Run data collection: python scripts/fetch_pr_data.py <pr_url>
  • Review generated artifacts in the workspace (e.g., /tmp/PRs/<repo>/<pr>/)
  • Generate review files: python scripts/generate_review_files.py /tmp/PRs/<repo>/<pr> --findings findings.json
  • Open the review directory for editing: /show
  • Post and approve when ready: /send or request changes: /send-decline

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 PR reviews with structured checks?

Automating GitHub PR reviews involves fetching metadata, diffs, and commits via the GitHub CLI, then analyzing changes against a quality checklist to generate structured internal and public review artifacts.

What is the best way to add inline comments to a PR during an automated code review?

Adding inline comments during a code review uses generated templates to provide code-specific feedback directly on the PR, which are only posted after completing a two-stage approval workflow.

Do I need to install Python and the GitHub CLI to automate PR data collection?

Yes, automating PR data collection requires the GitHub CLI and Python to fetch pull request metadata, diffs, commits, and related issues, with optional repository cloning for diff generation.

Can I extract and link JIRA or GitHub issues when automating a pull request review?

Yes, ticket tracking extracts and links JIRA and GitHub issue references automatically during the data collection phase to provide context for the structured pull request review.

How does the two-stage approval workflow prevent unwanted comments on GitHub PRs?

The two-stage approval workflow ensures nothing posts to GitHub until explicit approval is granted, keeping generated review files and inline comments internal during the editing phase.

What are the limitations of using automated scripts for GitHub PR reviews?

Automated PR review scripts depend on the GitHub CLI for data access and require manual execution of commands to generate findings, meaning they do not continuously monitor repositories or post automatically.