flow-next-rp-explorer

$npx mdskill add gmickel/flow-next/flow-next-rp-explorer

Explore codebases token-efficiently using RepoPrompt CLI commands.

  • Reduces token usage when exploring large codebases.
  • Depends on RepoPrompt Community Edition CLI (rpce-cli).
  • Activates when user says 'use rp' or 'use repoprompt' with an action.
  • Returns file structures, search results, or exported context.

SKILL.md

.github/skills/flow-next-rp-explorerView on GitHub ↗
---
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 Community Edition's 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](cli-reference.md) for complete command documentation.

## Quick Start

### Step 1: Get Overview
```bash
rpce-cli -e 'tree'
rpce-cli -e 'structure .'
```

### Step 2: Find Relevant Files
```bash
rpce-cli -e 'search "auth" --context-lines 2'
rpce-cli -e 'builder "understand authentication"'
```

### Step 3: Deep Dive
```bash
rpce-cli -e 'select set src/auth/'
rpce-cli -e 'structure --scope selected'
rpce-cli -e 'read src/auth/login.ts'
```

### Step 4: Export Context
```bash
rpce-cli -e 'context --all > codebase-map.md'
```

## Token Efficiency

- Use `structure` instead of reading full files (10x fewer tokens)
- Use `builder` for 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:
```bash
# Builder returns: Tab: <UUID> • <Name>
rpce-cli -w W -t "<Name>" -e 'select add extra.ts && context'

# Or chain commands:
rpce-cli -w W -e 'builder "find auth" && select add extra.ts && context'
```

## Requirements

RepoPrompt CE 1.1.0+ with `rpce-cli` installed. Direct Classic `rp-cli` instructions are intentionally not used; Classic is discontinued and survives only behind Flow-Next's wrapper compatibility ladder.

More from gmickel/flow-next

SkillDescription
flow-nextManage .flow/ tasks and specs. Use for show or list tasks, task status, what is ready, show fn-N. NOT for planning or executing (use the plan and work skills).
flow-next-auditAudit .flow/memory/ entries against current code and keep, update, consolidate, or delete each. Use when asked to audit or refresh memory.
flow-next-captureSynthesize the current conversation into a flow-next spec with read-back gating. Use when asked to capture this as a spec.
flow-next-depsShow spec dependency graph and execution order. Use when asking 'what's blocking what', 'execution order', 'dependency graph', 'what order should specs run', 'critical path', 'which specs can run in parallel'.
flow-next-driveDrive any UI surface like a real user - a web app, a Chromium-backed desktop app (Electron / WebView2, reached over CDP), or a genuinely native app (macOS AppKit/SwiftUI, or a non-CDP webview) reached via the Cua Driver / Computer Use. Detects the surface, picks the best available driver, degrades gracefully. Use to navigate sites, verify deployed UI, test web or desktop apps, capture baseline screenshots, drive a sign-in flow, scrape data, fill forms, run an e2e check, or inspect current page state. Triggers on "check the page", "verify UI", "test the site", "test this app", "drive the app", "automate this desktop app", "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", "Electron app", "native app".
flow-next-export-contextExport RepoPrompt context to a markdown file for review with an external LLM (ChatGPT, Claude web, etc.). Use when you want Carmack-level review but prefer an external model. Triggers on "export context", "export for external review", "export plan for ChatGPT", "export impl review context", "review with an external model", "export review context".
flow-next-impl-reviewCarmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.
flow-next-interviewIn-depth Q&A to refine a spec, task, or spec file before building. Use when asked to flesh out, refine, or interrogate requirements.
flow-next-landAutonomous PR babysitter tick. Fixes CI, resolves feedback, merges when converged, closes the spec, releases. Emits LAND_VERDICT. Use when asked to land PRs.
flow-next-make-prOpen a PR with a cognitive-aid body rendered from flow-next spec state via gh. Use whenever asked to make or open a PR in a flow-next repo.