メニュー
John Carmack-level implementation review via rp-cli for current branch changes. Use when reviewing code changes, PRs, or implementations. Triggers on mentions of code review, implementation review, or PR review.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | flow-impl-review |
| description | John Carmack-level implementation review via rp-cli for current branch changes. Use when reviewing code changes, PRs, or implementations. Triggers on mentions of code review, implementation review, or PR review. |
Conduct a John Carmack-level review of implementation changes on the current branch using RepoPrompt's context builder and chat.
Role: Code Review Coordinator (NOT the reviewer) Tool: rp-cli for context building and chat delegation
Arguments: #$ARGUMENTS
Format: [additional context, focus areas, or special instructions]
Example: /flow:impl-review focus on the auth changes, ignore styling
Reviews all changes on the current branch vs main/master.
The workflow gathers context from:
bd showDO NOT REVIEW CODE YOURSELF – you are a coordinator, not the reviewer.
Your job is to:
rp-cli -e 'windows' to find the RepoPrompt windowrp-cli -w <id> -e 'builder ...' to build contextrp-cli -w <id> -e 'chat ...' to execute the reviewThe RepoPrompt chat conducts the actual review with full file context.
Read workflow.md and follow each phase in order. Phases include change identification, context building, and review execution.
TodoWrite to track review iterations (e.g., "Round 1: Needs Work", "Round 2: Ship")timeout: 300 for long-running rp-cli commandsRead rp-cli-reference.md for command syntax and examples.
Carmack-level plan review via rp-cli context builder + chat. Use when reviewing implementation plans, architecture docs, or design specs. Triggers on mentions of plan review, design review, or architecture review.
Create structured build plans from feature requests, bug reports, or Beads issue IDs. Use when planning features, designing implementation, preparing work breakdown, or when given a bead/issue ID to plan. Triggers on /flow:plan with text descriptions or issue IDs (e.g., bd-123, gno-45, app-12).
Resume interrupted flow:work session from last checkpoint. Reads flow-progress.txt to restore context and continue work.
Execute a plan file or Beads epic systematically with git setup, task tracking, quality checks, and commit workflow. Use when implementing a plan, working through a spec, following documented steps, or executing a Beads issue ID (e.g., bd-123, gno-45, app-12).
Token-efficient codebase exploration using RepoPrompt CLI. Use when user says "use rp to..." or "use repoprompt to..." followed by explore, find, understand, search, or similar actions.
Manage git worktrees (create/list/switch/cleanup) and copy .env files. Use for parallel feature work, isolated review, clean workspace, or when user mentions worktrees.