rp-explorer
Scannednpx machina-cli add skill gmickel/gmickel-claude-marketplace/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/skills/rp-explorer/SKILL.mdView on GitHub Overview
RP-Explorer enables 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, guiding you through quick overviews, file discovery, deep dives, and context export. This workflow minimizes token usage by leveraging structure, builder, and selective context exports.
How This Skill Works
Start with a lightweight overview using rp-cli to map the tree and structure. Then use search and builder to locate relevant files, select a subset, and read only the essentials. Finally export the context to a codebase map or report to share with teammates.
When to Use It
- Exploring how authentication works in the repository.
- Finding similar patterns or implementations across modules.
- Understanding the data flow across components or services.
- Searching for API endpoints or integration points.
- Exporting a codebase map for onboarding or code reviews.
Quick Start
- Step 1: Get Overview with rp-cli -e 'tree' and 'structure .'
- Step 2: Find Relevant Files with rp-cli -e 'search "auth" --context-lines 2' and rp-cli -e 'builder "understand authentication"'
- Step 3: Deep Dive with 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.
- Leverage builder for AI-powered file discovery before diving in.
- Select only the relevant files before exporting context.
- Use isolated tabs for builder-driven exploration to keep context clean.
- Chain rp-cli commands (search → select → read → context) for a precise workflow.
Example Use Cases
- Audit authentication flow by listing the repo structure and inspecting src/auth/login.ts with rp-cli.
- Find authentication-related patterns with search and then discover with builder.
- Deep-dive into the login path: select set src/auth/, structure --scope selected, then read src/auth/login.ts.
- Create a codebase map with context --all > codebase-map.md for onboarding.
- Isolate a subset of files for a new engineer by using builder to identify relevant files and exporting the context.
