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.
Installation
Details
Usage
After installing, this skill will be available to your AI coding assistant.
Verify installation:
skills listSkill Instructions
name: flow-next-rp-explorer description: 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.
RP-Explorer
Token-efficient codebase exploration using RepoPrompt CLI.
Trigger Phrases
Activates when user combines "use rp" or "use repoprompt" with an action:
- "use rp to explore how auth works"
- "use repoprompt to find similar patterns"
- "use rp to understand the data flow"
- "use repoprompt to search for API endpoints"
CLI Reference
Read cli-reference.md for complete command documentation.
Quick Start
Step 1: Get Overview
rp-cli -e 'tree'
rp-cli -e 'structure .'
Step 2: Find Relevant Files
rp-cli -e 'search "auth" --context-lines 2'
rp-cli -e 'builder "understand authentication"'
Step 3: Deep Dive
rp-cli -e 'select set src/auth/'
rp-cli -e 'structure --scope selected'
rp-cli -e 'read src/auth/login.ts'
Step 4: Export Context
rp-cli -e 'context --all > codebase-map.md'
Token Efficiency
- Use
structureinstead of reading full files (10x fewer tokens) - Use
builderfor AI-powered file discovery - Select only relevant files before exporting context
Tab Isolation
builder creates an isolated compose tab automatically. Use -t to target it:
# Builder returns: Tab: <UUID> • <Name>
rp-cli -w W -t "<Name>" -e 'select add extra.ts && context'
# Or chain commands:
rp-cli -w W -e 'builder "find auth" && select add extra.ts && context'
Requirements
RepoPrompt v1.5.62+ with rp-cli installed.
More by gmickel
View allCarmack-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.
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.
Carmack-level plan review via RepoPrompt or Codex. Use when reviewing Flow epic specs or design docs. Triggers on /flow-next:plan-review.
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).
