prd-pr-review

Reviews GitHub pull requests in a tmux-backed interactive pi session using the active model.

Updated Nov 7, 2024
One-click install
npx skills add https://github.com/jeremysball/dotfiles --skill prd-pr-review-jeremysball
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-pr-review
Source: https://github.com/jeremysball/dotfiles/tree/main/.pi/skills-archive/prd-pr-review
Command: npx skills add https://github.com/jeremysball/dotfiles --skill prd-pr-review-jeremysball

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Reviewing a pull request often requires repeated back-and-forth passes with full PR context, and manually assembling the diff, comments, and review history for each pass is tedious. This Skill automates that gathering and launches an interactive review session that persists across follow-up questions. ## Core Features & Use Cases - Automated PR context gathering: Fetches PR metadata, diff, issue comments, inline review comments, and review history via the GitHub CLI. - Model continuity: Detects the most recent local pi session for the working directory and reuses its active model and thinking level for the review. - Interactive tmux review sessions: Launches a detached tmux session running pi with the PR context preloaded, so follow-up questions continue in the same pane; a one-shot --print mode is available for single passes. - Use Case: After finishing a feature with /prd-done, run the script with the PR URL to get a structured review (summary, severity-bucketed findings, questions, next steps), then attach to the tmux session to ask follow-up questions before merging. ## Quick Start Ask the assistant to review a GitHub pull request by providing its URL, for example by saying to review PR https://github.com/owner/repo/pull/123 with a focus on tests and documentation.

Frequently Asked Questions about prd-pr-review

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

FAQPage Schema
How do I review a GitHub pull request from the terminal?

Run the review script with a PR URL, number, or branch, and it fetches the metadata, diff, and comments with the gh CLI, then opens an interactive review session. Use the --print flag for a one-shot review instead.

How do I review a PR with the same AI model as my current session?

The script locates the most recent local pi session for the current working directory and extracts its active model and thinking level. If no session is found, it falls back to pi's configured default model.

What tools are required to run this PR review workflow?

The GitHub CLI (gh) and pi are required, and the script stops with an error if gh is missing. tmux is optional; without it, the script falls back to a one-shot printed review.

Can I continue asking follow-up questions after the initial PR review?

Yes, the review runs in a detached tmux session that stays open for follow-up questions. Reattach with tmux attach -t <session-name>, and rerunning the script for the same PR points you to the existing session.

What happens when a pull request diff is too large to review?

The script truncates the diff to 1200 lines by default and notes the truncation in the prompt. You can adjust the limit with the --max-diff-lines option when launching the review.