Menu
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
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| 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} |
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.
/review-pr <PR number or URL>
Accepts: 207, #207, or https://github.com/.../pull/207
Extract the PR number from the argument. Strip # prefix or extract from URL path.
ralph run -H ralph.reviewer.yml -p "Review PR #<N>"
Bash tool settings:
timeout: 600000 (10 minutes)run_in_background: trueUse TaskOutput with block: true to wait for completion.
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:
.ralph/review-scope.md — what was scoped.ralph/review-verification.md — test results.ralph/review-findings.md — review findingsCheck that the review worktree was removed:
ls -d .worktrees/review-<N> 2>/dev/null
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.
| 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 |
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.
Use when testing Ralph's hat collection presets, validating preset configurations, or auditing the preset library for bugs and UX issues.
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.
Introspect, explain, and improve Ralph Orchestrator using its published llms.txt doc map. Use this skill whenever the user asks questions about Ralph's behavior, wants to understand how a Ralph internal works (event loop, hats, memories, tasks, backends, presets), debug an unfamiliar failure mode, or propose a code change to the ralph-orchestrator repo. The skill teaches the agent to discover authoritative answers from the live docs via llms.txt before guessing, and to scope improvements through the published architecture rather than the local checkout alone.
Run, monitor, resume, merge, and debug Ralph loops. Use this skill whenever the user asks to operate `ralph run` or `ralph loops`, inspect loop state, recover suspended loops, analyze diagnostics, or unblock merge queue issues.
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.