Best use case
repoprompt is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use RepoPrompt CLI for token-efficient codebase exploration
Teams using repoprompt should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/repoprompt/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How repoprompt Compares
| Feature / Agent | repoprompt | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use RepoPrompt CLI for token-efficient codebase exploration
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# RepoPrompt Skill
## When to Use
- **Explore codebase structure** (tree, codemaps)
- **Search code** with context lines
- **Get code signatures** without full file content (token-efficient)
- **Read file slices** (specific line ranges)
- **Build context** for tasks
## Token Optimization
RepoPrompt is **more token-efficient** than raw file reads:
- `structure` → signatures only (not full content)
- `read --start-line --limit` → slices instead of full files
- `search --context-lines` → relevant matches with context
## CLI Usage
```bash
# If installed to PATH (Settings → MCP Server → Install CLI to PATH)
rp-cli -e 'command'
# Or use the alias (configure in your shell)
repoprompt_cli -e 'command'
```
## Commands Reference
### File Tree
```bash
# Full tree
rp-cli -e 'tree'
# Folders only
rp-cli -e 'tree --mode folders'
# Selected files only
rp-cli -e 'tree --mode selected'
```
### Code Structure (Codemaps) - TOKEN EFFICIENT
```bash
# Structure of specific paths
rp-cli -e 'structure src/auth/'
# Structure of selected files
rp-cli -e 'structure --scope selected'
# Limit results
rp-cli -e 'structure src/ --max-results 10'
```
### Search
```bash
# Basic search
rp-cli -e 'search "pattern"'
# With context lines
rp-cli -e 'search "error" --context-lines 3'
# Filter by extension
rp-cli -e 'search "TODO" --extensions .ts,.tsx'
# Limit results
rp-cli -e 'search "function" --max-results 20'
```
### Read Files - TOKEN EFFICIENT
```bash
# Full file
rp-cli -e 'read path/to/file.ts'
# Line range (slice)
rp-cli -e 'read path/to/file.ts --start-line 50 --limit 30'
# Last N lines (tail)
rp-cli -e 'read path/to/file.ts --start-line -20'
```
### Selection Management
```bash
# Add files to selection
rp-cli -e 'select add src/auth/'
# Set selection (replace)
rp-cli -e 'select set src/api/ src/types/'
# Clear selection
rp-cli -e 'select clear'
# View current selection
rp-cli -e 'select get'
```
### Workspace Context
```bash
# Get full context
rp-cli -e 'context'
# Specific includes
rp-cli -e 'context --include prompt,selection,tree'
```
### Chain Commands
```bash
# Multiple operations
rp-cli -e 'select set src/auth/ && structure --scope selected && context'
```
### Workspaces
```bash
# List workspaces
rp-cli -e 'workspace list'
# List tabs
rp-cli -e 'workspace tabs'
# Switch workspace
rp-cli -e 'workspace switch "ProjectName"'
```
### AI Chat (uses RepoPrompt's models)
```bash
# Send to chat
rp-cli -e 'chat "How does the auth system work?"'
# Plan mode
rp-cli -e 'chat "Design a new feature" --mode plan'
```
### Context Builder (AI-powered file selection)
```bash
# Auto-select relevant files for a task
rp-cli -e 'builder "implement user authentication"'
```
## Workflow Shorthand Flags
```bash
# Quick operations without -e syntax
rp-cli --workspace MyProject --select-set src/ --export-context ~/out.md
rp-cli --chat "How does auth work?"
rp-cli --builder "implement user authentication"
```
## Script Files (.rp)
For repeatable workflows, save commands to a script:
```bash
# daily-export.rp
workspace switch Frontend
select set src/components/
context --all > ~/exports/frontend.md
```
Run with:
```bash
rp-cli --exec-file ~/scripts/daily-export.rp
```
## CLI Flags
| Flag | Purpose |
|------|---------|
| `-e 'cmd'` | Execute command(s) |
| `-w <id>` | Target window ID |
| `-q` | Quiet mode |
| `-d <cmd>` | Detailed help for command |
| `--wait-for-server 5` | Wait for connection (scripts) |
## Async Operations (tmux)
For long-running operations like `builder`, use the async script:
```bash
# Start context builder async
uv run python -m runtime.harness scripts/repoprompt_async.py \
--action start --task "understand the auth system"
# With workspace switch
uv run python -m runtime.harness scripts/repoprompt_async.py \
--action start --workspace "MyProject" --task "explore API patterns"
# Check status
uv run python -m runtime.harness scripts/repoprompt_async.py --action status
# Get result when done
uv run python -m runtime.harness scripts/repoprompt_async.py --action result
# Kill if needed
uv run python -m runtime.harness scripts/repoprompt_async.py --action kill
```
## Note
Requires RepoPrompt app running with MCP Server enabled.Related Skills
workflow-router
Goal-based workflow orchestration - routes tasks to specialist agents based on user goals
wiring
Wiring Verification
websocket-patterns
Connection management, room patterns, reconnection strategies, message buffering, and binary protocol design.
visual-verdict
Screenshot comparison QA for frontend development. Takes a screenshot of the current implementation, scores it across multiple visual dimensions, and returns a structured PASS/REVISE/FAIL verdict with concrete fixes. Use when implementing UI from a design reference or verifying visual correctness.
verification-loop
Comprehensive verification system covering build, types, lint, tests, security, and diff review before a PR.
vector-db-patterns
Embedding strategies, ANN algorithms, hybrid search, RAG chunking strategies, and reranking for semantic search and retrieval.
variant-analysis
Find similar vulnerabilities across a codebase after discovering one instance. Uses pattern matching, AST search, Semgrep/CodeQL queries, and manual tracing to propagate findings. Adapted from Trail of Bits. Use after finding a bug to check if the same pattern exists elsewhere.
validate-agent
Validation agent that validates plan tech choices against current best practices
tracing-patterns
OpenTelemetry setup, span context propagation, sampling strategies, Jaeger queries
tour
Friendly onboarding tour of Claude Code capabilities for users asking what it can do.
tldr-stats
Show full session token usage, costs, TLDR savings, and hook activity
tldr-router
Map code questions to the optimal tldr command by detecting intent and routing to the right analysis layer.