repomix

Pack local or remote repositories into a single context blob for whole-codebase analysis.

2|3|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/spideynolove/claude-dotfiles --skill repomix-spideynolove
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repomix
Source: https://github.com/spideynolove/claude-dotfiles/tree/main/.claude-global/skills/repomix
Command: npx skills add https://github.com/spideynolove/claude-dotfiles --skill repomix-spideynolove

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Understanding an entire codebase requires reading dozens of files across many directories, which is slow and error-prone. This Skill packs a whole repository into one structured output file so an AI or human can reason about architecture, cross-file consistency, and unfamiliar codebases in a single pass. ## Core Features & Use Cases - Repository Packing: Bundle a local directory or remote GitHub repo into XML, Markdown, JSON, or plain text output with directory structure and file summaries. - Token Compression: Use Tree-sitter-based compression to strip implementation bodies and keep only signatures, reducing token count by roughly 70% for large repos. - Configurable Filtering: Respect .gitignore and custom ignore patterns, with token counting via the o200k_base encoding to keep output within context limits. - Use Case: Before writing an architecture spec that spans multiple modules, run repomix on the project root and feed the resulting XML blob into the planning stage instead of opening files one by one. ## Quick Start Ask the AI to pack the current repository with repomix and summarize its architecture from the generated output file.

Frequently Asked Questions about repomix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I pack a repository into a single file with repomix?

Run repomix in the project root to generate an AI-optimized XML file by default. Use --style markdown for human-readable output, or --remote user/repo to pack a GitHub repository without cloning it first.

How do I reduce repomix output token count for large repos?

Enable compression with repomix --compress, which uses Tree-sitter to keep only function signatures and structure while discarding implementation bodies. This reduces token count by roughly 70%, and you can further narrow scope with includePatterns.

Can repomix pack a remote GitHub repository?

Yes, repomix supports remote packing via repomix --remote user/repo, with an optional --remote-branch flag to target a specific branch. The output is written locally like a normal pack operation.

When should I not use repomix for codebase analysis?

Avoid repomix for single-file edits, simple bug fixes, or tasks where the relevant files are already open. It is designed for whole-repository understanding, so using it on narrow tasks wastes tokens and adds no value.

Why do repomix MCP tools fail with Unknown MCP server?

The repomix MCP tools only work when repomix is registered as a persistent MCP server with autoStart enabled in settings. By default it is not registered, so use the repomix CLI commands instead.