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
The English summary is being prepared. Showing the original description.
Review the instructions the agent will receive before you install.
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 |
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Use when testing Ralph's hat collection presets, validating preset configurations, or auditing the preset library for bugs and UX issues.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Transforms a rough idea into a detailed design document with implementation plan. Follows Prompt-Driven Development — iterative requirements clarification, research, design, and planning.
The English summary is being prepared. Showing the original description.
Browser automation via Playwriter (remorses) using persistent Chrome sessions and the full Playwright Page API.
The English summary is being prepared. Showing the original description.