flow-next-rp-explorer
Scannednpx machina-cli add skill gmickel/gmickel-claude-marketplace/flow-next-rp-explorer --openclawRP-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.
Source
git clone https://github.com/gmickel/gmickel-claude-marketplace/blob/main/plugins/flow-next/skills/flow-next-rp-explorer/SKILL.mdView on GitHub Overview
RP-Explorer delivers token-efficient codebase exploration using the RepoPrompt CLI. It activates when you say "use rp" or "use repoprompt" followed by actions like explore, find, understand, or search, helping you quickly map, locate, and inspect the codebase.
How This Skill Works
The skill guides you through four stages: overview, find relevant files, deep dive, and export context. It emphasizes token savings by using structure instead of full-file reads, using builder for AI-powered discovery, and selecting only relevant files before exporting to a codebase map.
When to Use It
- You want to quickly understand how a subsystem works (e.g., authentication) using rp to explore and understand.
- You need to locate and compare similar patterns across the repository with search and builder.
- You aim to trace data flow and see how components connect within the codebase.
- You’re looking for API endpoints and their usage in a flow-next project.
- You want to export a codebase map (codebase-map.md) for teammates or 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'
Best Practices
- Use structure instead of reading full files to save tokens (10x fewer tokens).
- Use builder for AI-powered file discovery to surface relevant areas quickly.
- Select only relevant files before exporting context to keep the map focused.
- Isolate work in a dedicated tab/session when using builder for clean context.
- Chain commands to minimize back-and-forth and maintain a cohesive workflow.
Example Use Cases
- Explore how authentication flows work in a Next.js app and map the involved files.
- Find and compare similar authentication patterns across services in the repo.
- Map the data flow for a user login sequence from UI to API.
- Search for API endpoints used by a feature and list their call sites.
- Export a codebase map (codebase-map.md) to share with teammates.
