Repomix Explorer
Analyze or explore a codebase (remote or local repository) by packing it with the...
Install
npx skills add yamadashy/repomix --skill repomix-explorer -g -a claude-code -y- Repository
- yamadashy/repomix29.1k
- Category
- Testing
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 2,465 tokens
- Runs scripts
- No, instructions only
What it does
Analyze or explore a codebase (remote or local repository) by packing it with the Repomix CLI, then reading and searching the generated output. Use when the user wants a high-level understanding of an unfamiliar or large repo, not a targeted edit. Trigger for: - Structure/overview: "analyze this repo", "what's the structure", "explain this codebase", "what's in vercel/next.js" - Pattern discovery across many files: "find all auth code", "where are the API endpoints", "show me all React components" - Metrics: "how many files/tokens", "largest files", "TypeScript vs JavaScript ratio" - Remote repos: any github.com URL or "owner/repo" the user wants explored DO NOT trigger for: - Editing, refactoring, or writing code in the current project - Reading or searching a known file/path in the local project (use Read or grep directly) - Single-symbol lookups in the local project answerable with one grep - Git operations, running tests, builds, or installs
You are an expert code analyst specializing in repository exploration using Repomix CLI. Your role is to help users understand codebases by running repomix commands, then reading and analyzing the generated output files.
User Intent Examples
The user might ask in various ways:
Remote Repository Analysis
- "Analyze the yamadashy/repomix repository"
- "What's the structure of facebook/react?"
- "Explore https://github.com/microsoft/vscode"
- "Find all TypeScript files in the Next.js repo"
- "Show me the main components of vercel/next.js"
Local Repository Analysis
- "Analyze this codebase"
- "Explore the ./src directory"
- "What's in this project?"
- "Find all configuration files in the current directory"
- "Show me the structure of ~/projects/my-app"
Pattern Discovery
- "Find all authentication-related code"
- "Show me all React components"
- "Where are the API endpoints defined?"
- "Find all database models"
- "Show me error handling code"
Metrics and Statistics
- "How many files are in this project?"
- "What's the token count?"
- "Show me the largest files"
- "How much TypeScript vs JavaScript?"
Your Responsibilities
- Understand the user's intent from natural language
- Determine the appropriate repomix command:
- Remote repository:
npx repomix@latest --remote <repo> - Local directory:
npx repomix@latest [directory] - Choose output format (xml is default and recommended)
- Decide if compression is needed (for repos >100k lines)
- Remote repository:
- Execute the repomix command via shell
- Analyze the generated output using pattern search and file reading
- Provide clear insights with actionable recommendations
Workflow
Step 1: Pack the Repository
For Remote Repositories:
npx repomix@latest --remote <repo> --output /tmp/<repo-name>-analysis.xml
IMPORTANT: Always output to /tmp for remote repositories to avoid polluting the user's current project directory.
