How do I install the Flow Impl Review skill?

Run npx skillmds@latest add tomevault-io/flow-impl-review in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Flow Impl Review safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Flow Impl Review?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Flow Impl Review free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Flow Impl Review?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Flow Impl Review by tomevault-io — Agent Skill

Name: Flow Impl Review
Author: tomevault-io

Flow Impl Review

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. Use when this capability is needed.

tomevault-io cd92dec 2 files · 3.2 KB Updated Sep 17, 2026

File contents

Implementation Review Mode (CLI)

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

Input

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.

FIRST: Determine Review Mode

Check: which rp-cli >/dev/null 2>&1 If NOT available: inform user rp-cli is required for this skill.

If review mode was already chosen earlier in this conversation (e.g., user answered "2a" or "2b" during /flow:plan or /flow:work setup): → Use that mode, don't ask again.

If invoked directly without prior context, ask:

Both modes use RepoPrompt for context building (builder, file selection, codemaps).
The difference is where the review happens:

Review mode:
a) RepoPrompt chat (default) — review via rp-cli chat
b) Export for external LLM — export context file for ChatGPT, Claude web, etc.

(Reply: "a", "b", "export", or just tell me)

Wait for response. Parse naturally.

Context Sources

The workflow gathers context from:

Git diff and commit messages
Plan files referenced in commits
PRD/architecture docs
Beads: If you know which issue(s) this work relates to, include via bd show

Critical Requirement

DO NOT REVIEW CODE YOURSELF – you are a coordinator, not the reviewer.

Your job is to:

Use rp-cli -e 'windows' to find the RepoPrompt window
Use rp-cli -w <id> -e 'builder ...' to build context
Use rp-cli -w <id> -e 'chat ...' to execute the review

The RepoPrompt chat conducts the actual review with full file context.

Workflow

Read workflow.md and follow each phase in order. Phases include change identification, context building, and review execution.

rp-cli Reference

Read rp-cli-reference.md for command syntax and examples.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: flow-impl-reviewdescription: 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. Use when this capability is needed.---# Implementation Review Mode (CLI)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## InputArguments: #$ARGUMENTSFormat: `[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.## FIRST: Determine Review ModeCheck: `which rp-cli >/dev/null 2>&1`If NOT available: inform user rp-cli is required for this skill.**If review mode was already chosen earlier in this conversation** (e.g., user answered "2a" or "2b" during `/flow:plan` or `/flow:work` setup):→ Use that mode, don't ask again.**If invoked directly without prior context**, ask:```Both modes use RepoPrompt for context building (builder, file selection, codemaps).The difference is where the review happens:Review mode:a) RepoPrompt chat (default) — review via rp-cli chatb) Export for external LLM — export context file for ChatGPT, Claude web, etc.(Reply: "a", "b", "export", or just tell me)```Wait for response. Parse naturally.## Context SourcesThe workflow gathers context from:- Git diff and commit messages- Plan files referenced in commits- PRD/architecture docs- **Beads**: If you know which issue(s) this work relates to, include via `bd show`## Critical Requirement**DO NOT REVIEW CODE YOURSELF** – you are a coordinator, not the reviewer.Your job is to:1. Use `rp-cli -e 'windows'` to find the RepoPrompt window2. Use `rp-cli -w <id> -e 'builder ...'` to build context3. Use `rp-cli -w <id> -e 'chat ...'` to execute the reviewThe **RepoPrompt chat** conducts the actual review with full file context.## WorkflowRead [workflow.md](workflow.md) and follow each phase in order. Phases include change identification, context building, and review execution.## rp-cli ReferenceRead [rp-cli-reference.md](rp-cli-reference.md) for command syntax and examples.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/gmickel) — claim your Tome and manage your conversions.

Frequently asked questions