/review-pr
Use when asked to review a PR, run a code review loop, or invoke the ralph reviewer against a pull request number or GitHub URL
$ npx -y skills add mikeyobrien/ralph-orchestrator --skill review-pr --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/review-pr
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when asked to review a PR, run a code review loop, or invoke the ralph reviewer against a pull request number or GitHub URL
SKILL.md
review-pr.SKILL.mdname: review-pr
description: Use when asked to review a PR, run a code review loop, or invoke the ralph reviewer against a pull request number or GitHub URL
metadata:
internal: true
Review PR
Run the `ralph.reviewer.yml` orchestration loop against a pull request. The loop checks out the PR in an isolated worktree, runs tests, reviews the diff, and produces a structured report.
Usage
/review-pr <PR number or URL>
Accepts: `207`, `#207`, or `https://github.com/.../pull/207`
Execution
1. Parse the PR argument
Extract the PR number from the argument. Strip `#` prefix or extract from URL path.
2. Run the reviewer loop
ralph run -H ralph.reviewer.yml -p "Review PR #<N>"
**Bash tool settings:**
- `timeout: 600000` (10 minutes)
- `run_in_background: true`
Use `TaskOutput` with `block: true` to wait for completion.
3. Display the report
Read and print `.ralph/REVIEW-REPORT.md` to the conversation.
If the report file doesn't exist (loop failed before the synthesizer hat), check for and display whatever intermediate files exist: 1. `.ralph/review-scope.md` — what was scoped 2. `.ralph/review-verification.md` — test results 3. `.ralph/review-findings.md` — review findings
4. Verify cleanup
Check that the review worktree was removed:
ls -d .worktrees/review-<N> 2>/dev/null
- If gone: cleanup succeeded, no action needed.
- If still present: **warn the user** but do NOT force-remove. Say what's there and let them decide.
Also note the presence of intermediate files (`.ralph/review-scope.md`, etc.) — they're useful for debugging but the user may want to clean them up later.
Error Handling
| Situation | Action | |-----------|--------| | Ralph exits non-zero | Display error output. Suggest re-running with `RALPH_DIAGNOSTICS=1` | | Report file missing | Display intermediate files that do exist (scope, verification, findings) | | PR argument missing | Ask the user for the PR number | | PR argument unparseable | Ask the user to provide a bare number, `#N`, or full GitHub URL |
What This Skill Does NOT Do
- Does NOT validate the PR exists (the scoper hat handles that)
- Does NOT modify any source code (read-only review)
- Does NOT post comments to GitHub
- Does NOT own worktree cleanup (verifies only)
- Does NOT enable diagnostics by default
Read more
name: review-pr description: Use when asked to review a PR, run a code review loop, or invoke the ralph reviewer against a pull request number or GitHub URL metadata: internal: true
Review PR
Run the `ralph.reviewer.yml` orchestration loop against a pull request. The loop checks out the PR in an isolated worktree, runs tests, reviews the diff, and produces a structured report.
Usage
/review-pr <PR number or URL>
Accepts: `207`, `#207`, or `https://github.com/.../pull/207`
Execution
1. Parse the PR argument
Extract the PR number from the argument. Strip `#` prefix or extract from URL path.
2. Run the reviewer loop
ralph run -H ralph.reviewer.yml -p "Review PR #<N>"
**Bash tool settings:**
- `timeout: 600000` (10 minutes)
- `run_in_background: true`
Use `TaskOutput` with `block: true` to wait for completion.
3. Display the report
Read and print `.ralph/REVIEW-REPORT.md` to the conversation.
If the report file doesn't exist (loop failed before the synthesizer hat), check for and display whatever intermediate files exist: 1. `.ralph/review-scope.md` — what was scoped 2. `.ralph/review-verification.md` — test results 3. `.ralph/review-findings.md` — review findings
4. Verify cleanup
Check that the review worktree was removed:
ls -d .worktrees/review-<N> 2>/dev/null
- If gone: cleanup succeeded, no action needed.
- If still present: **warn the user** but do NOT force-remove. Say what's there and let them decide.
Also note the presence of intermediate files (`.ralph/review-scope.md`, etc.) — they're useful for debugging but the user may want to clean them up later.
Error Handling
| Situation | Action | |-----------|--------| | Ralph exits non-zero | Display error output. Suggest re-running with `RALPH_DIAGNOSTICS=1` | | Report file missing | Display intermediate files that do exist (scope, verification, findings) | | PR argument missing | Ask the user for the PR number | | PR argument unparseable | Ask the user to provide a bare number, `#N`, or full GitHub URL |
What This Skill Does NOT Do
- Does NOT validate the PR exists (the scoper hat handles that)
- Does NOT modify any source code (read-only review)
- Does NOT post comments to GitHub
- Does NOT own worktree cleanup (verifies only)
- Does NOT enable diagnostics by default
A hat-based orchestration framework that keeps AI agents in a loop until the task is done. "Me fail English? That's unpossible!" - Ralph Wiggum
Repo: mikeyobrien/ralph-orchestrator
Other skills on ralph-orchestrator.
- /code-assist
Guides implementation of code tasks using test-driven development in an Explore, Plan, Code, Commit workflow. Acts as a Technical Implementation Partner and TDD Coach — following existing patterns, avoiding over-engineering, and producing idiomatic, modern code.
Open skill - /code-task-generator
Generates structured .code-task.md files from descriptions or PDD implementation plans. Auto-detects input type, creates properly formatted tasks with Given-When-Then acceptance criteria.
Open skill - /evaluate-presets
Use when testing Ralph's hat collection presets, validating preset configurations, or auditing the preset library for bugs and UX issues.
Open skill - /find-code-tasks
Lists all code tasks in the repository with their status, dates, and metadata. Useful for getting an overview of pending work or finding specific tasks.
Open skill - /pdd
Transforms a rough idea into a detailed design document with implementation plan. Follows Prompt-Driven Development — iterative requirements clarification, research, design, and planning.
Open skill - /playwriter
Browser automation via Playwriter (remorses) using persistent Chrome sessions and the full Playwright Page API.
Open skill

