gmickel/rp-explorer
plugins/flow/skills/rp-explorer/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add gmickel/gmickel-claude-marketplace rp-explorerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 5, 2026, 1:25 PM5.1s2 files scanned
SKILL.md
- name:
- 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.
Related Skills
gmickel/flow-next-make-pr
data-ai
VerifiedTrustedCommunity
Render a cognitive-aid PR body from flow-next state and open via gh. Triggers on /flow-next:make-pr with optional spec id and flags (--draft, --ready, --no-mermaid, --base <ref>, --memory, --dry-run). Auto-detects spec from current branch when no id given. NOT Ralph-blocked — autonomous loops can surface a draft PR for human review.
630SKILL.mdUpdated May 8, 2026
gmickel/flow-next-make-pr
data-ai
VerifiedTrustedCommunity
Render a cognitive-aid PR body from flow-next state and open via gh. Triggers on /flow-next:make-pr with optional spec id and flags (--draft, --ready, --no-mermaid, --base <ref>, --memory, --dry-run). Auto-detects spec from current branch when no id given. NOT Ralph-blocked — autonomous loops can surface a draft PR for human review.
630SKILL.mdUpdated May 8, 2026
gmickel/flow-next-capture
testing
VerifiedTrustedCommunity
Synthesize the current conversation context into a flow-next spec at `.flow/specs/<spec-id>.md` via `flowctl spec create + spec set-plan` — agent-native, source-tagged, with mandatory read-back before write. Triggers on /flow-next:capture, "capture spec", "lock down what we discussed", "make a spec from this conversation", "convert conversation to spec". Optional `mode:autofix` token runs without questions and requires `--yes` to commit. Optional `--rewrite <spec-id>` overwrites an existing spec; `--from-compacted-ok` overrides the compaction-detection refusal; `--override-strategy` proceeds despite a contradiction with an active STRATEGY.md track (and prompts to record the override as a decision).
630SKILL.mdUpdated Apr 26, 2026
gmickel/flow-next-capture
testing
VerifiedTrustedCommunity
Synthesize the current conversation context into a flow-next spec at `.flow/specs/<spec-id>.md` via `flowctl spec create + spec set-plan` — agent-native, source-tagged, with mandatory read-back before write. Triggers on /flow-next:capture, "capture spec", "lock down what we discussed", "make a spec from this conversation", "convert conversation to spec". Optional `mode:autofix` token runs without questions and requires `--yes` to commit. Optional `--rewrite <spec-id>` overwrites an existing spec; `--from-compacted-ok` overrides the compaction-detection refusal; `--override-strategy` proceeds despite a contradiction with an active STRATEGY.md track (and prompts to record the override as a decision).
630SKILL.mdUpdated Apr 26, 2026