Repomix packages repository files into one AI-readable document. Use it to give a reviewer a scoped view of source code and directory structure. Choose the files first, inspect the output for secrets and irrelevant generated content, and then supply that document to your coding agent.
Install and choose a working environment
Tool version 1.19.0. Documentation checked 2026-11-16. The upstream source snapshot and installed package are pinned separately; the snapshot is not claimed to be the package’s release commit.
node --version
npx -y repomix@1.19.0 --help
npx -y repomix@1.19.0 . --output review.xml
This package is a CLI/Python library, not an MCP server configured by the install command above. Run the examples in the project’s environment and give the resulting files to your assistant.
- Claude Code: open the project, ask it to inspect the saved script/output, and confirm the interpreter path before execution.
- Codex: open the same workspace, provide the script/output filename, and ask for a review or a locally permitted run.
- Cursor: choose the project’s Python interpreter, run the command in its terminal, then attach the resulting file in chat.
These are file/terminal workflows, not a claim of a vendor-specific integration. The three client interfaces were not tested locally.
Three practical uses
1. Package a focused review
npx -y repomix@1.19.0 . --include "src/**,README.md" --output review.xml
Expected: Check that review.xml contains the intended source paths and their contents.
2. Exclude private and generated files
npx -y repomix@1.19.0 . --ignore "private/**,dist/**,*.log" --output review.xml
Expected: Inspect the output to confirm excluded files are absent. Ignore patterns do not certify it secret-free.
3. Request an evidence-based review
Review review.xml for error handling and input validation. Cite the file, code excerpt and reproduction condition for each finding; do not assume omitted files.
Expected: a response that follows the stated scope and exposes the requested source or tool result. Verify those references before acting.
What our tests established
The isolated 1.19.0 run retained known text and code, excluded specified private/log files and left inputs unchanged. A missing directory failed. Large repositories, model understanding after compression and private remote repositories were not tested.
Tests were run by Codex on synthetic data; no claim of the owner personally testing or reviewing this guide. Examples added above are documentation-based unless included in that recorded scope.
Common errors and fixes
Packed output is too large
Limit --include to the files needed for one question.
A private file is included
Add explicit exclusions, regenerate, and inspect both filenames and content before sharing.
Input directory does not exist
Verify the working directory and input path; the recorded CLI rejected a missing directory.
Limits, costs and license
MIT. Local packaging does not include free inference. Your output still carries the source project’s licensing and confidentiality obligations; inspect it before sharing.
When to choose an alternative
-
For a small, simple file-to-prompt task: files-to-prompt.
-
For separate repository summary, tree and content: Gitingest.
FAQ
How do I use Repomix with Claude Code?
Generate review.xml with the CLI, then ask Claude Code to read it. This basic path needs no MCP integration.
What are the alternatives to Repomix?
Compare files-to-prompt for a few files and Gitingest for summary/tree/content output.
Can it package a GitHub repository?
The project documents remote inputs, but the recorded test covers a local directory only.
Official sources
For another repository digest, see Gitingest's output checks. If you only need selected files combined as text, compare files-to-prompt's file selection.