repomix-explorer
Use this skill when the user wants to analyze or explore a codebase (remote repository or local repository) using Repomix. Triggers on: 'analyze this repo', 'explore codebase', 'what's the structure', 'find patterns in repo', 'how many files/tokens'. Runs repomix CLI to pack repositories, then analyzes the output.
npx skills add majiayu000/claude-skill-registry --skill repomix-explorer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
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 1. **Understand the user's intent** from na
- User Intent Examples
- Remote Repository Analysis
- Local Repository Analysis
- Pattern Discovery
- Metrics and Statistics
- Your Responsibilities
- Workflow
- Step 1: Pack the Repository
- Step 2: Check Command Output
- Step 3: Analyze the Output File
- Step 4: Provide Insights
- Best Practices
- Efficiency
- Output Format
npx repomix@latest --remote <repo> --output /tmp/<repo-name>-analysis.xml npx repomix@latest [directory] [options] Basic remote pack (always use /tmp) npx repomix@latest --remote yamadashy/repomix --output /tmp/repomix-analysis.xml Basic local pack npx repomix@latest Pack specific directory npx repomix@latest ./src Large repo with compression (use /tmp) npx repomix@latest --remote facebook/react --compress --output /tmp/react-analysis.xml
What does the repomix-explorer skill do?
Use this skill when the user wants to analyze or explore a codebase (remote repository or local repository) using Repomix. Triggers on: 'analyze this repo', 'explore codebase', 'what's the structure', 'find patterns in repo', 'how many files/tokens'. Runs repomix CLI to pack repositories, then analyzes the output.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill repomix-explorer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.