flow-next-opencode-rp-explorer
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 from gmickel/flow-next-opencode
browser
Browser automation via agent-browser CLI. Use when you need to navigate websites, verify deployed UI, test web apps, read online documentation, scrape data, fill forms, capture baseline screenshots before design work, or inspect current page state. Triggers on "check the page", "verify UI", "test the site", "read docs at", "look up API", "visit URL", "browse", "screenshot", "scrape", "e2e test", "login flow", "capture baseline", "see how it looks", "inspect current", "before redesign".
1flow-next-opencode-plan
Create structured build plans from feature requests or Flow IDs. Use when planning features or designing implementation. Triggers on /flow-next:plan with text descriptions or Flow IDs (fn-1, fn-1.2).
1flow-next-opencode-sync
Manually trigger plan-sync to update downstream task specs after implementation drift. Use when code changes outpace specs.
1flow-next-opencode-work
Execute a Flow epic or task systematically with git setup, task tracking, quality checks, and commit workflow. Use when implementing a plan or working through a spec. Triggers on /flow-next:work with Flow IDs (fn-1, fn-1.2).
1flow-next-opencode
Manage .flow/ tasks and epics. Triggers: 'show me my tasks', 'list epics', 'what tasks are there', 'add a task', 'create task', 'what's ready', 'task status', 'show fn-1'. NOT for /flow-next:plan or /flow-next:work.
1flow-next-opencode-prime
Comprehensive codebase assessment for agent and production readiness. Scans 8 pillars (48 criteria), verifies commands work, checks GitHub settings. Reports everything, fixes agent readiness only. Triggers on /flow-next:prime.
1