Repeatable file selection is the reason to try Repomix
Repomix writes selected repository content to repomix-output.xml by default. Its output includes a directory structure, source content and instructions for the receiving assistant. Include patterns and ignore rules let developers define the files needed for recurring questions about a codebase.
The Repomix README documents support for .gitignore, .ignore and .repomixignore, along with token counts for individual files and the overall repository. These controls help readers inspect the scope and size of a pack. Our run did not measure whether a receiving model understood it or produced correct answers.
What happened when we ran it
Our October 6, 2026 run at commit 8d64291 installed 356 dependencies in 8 seconds and used 296 MB on disk. The build succeeded in 2 seconds. Vitest passed all 1,843 tests in 27 seconds, with 0 failures.
npm audit reported 8 known vulnerabilities: 1 critical, 6 high and 1 moderate. The supplied record does not identify the affected packages or distinguish development dependencies from deployed paths. Those details are needed to assess exposure or recommend a dependency change. Passing tests do not resolve dependency advisories.
The recorded setup specified 3 CPUs, 8 GB RAM and image lab-node:22. That label does not establish the actual Node version or operating system. The checkout contained 1,182 files and approximately 66,536 source lines. The scanner recorded 21 CI workflow files, a Dockerfile and a tests directory.
These measurements belong to the October 6 checkout. They do not establish the dependency or test status of a later checkout or release.
Compression removes implementation details
The README says Tree-sitter compression focuses on function and class signatures while removing implementation details. That can help with an initial structural overview, but it can omit the branch or statement needed to explain a bug.
Keep full content for the functions under investigation. This is a recommendation based on the documented omission of implementation details, not a result from comparing compressed and complete packs. We measured neither compression savings nor model answer quality.
A token-budget failure still leaves an output file
The documented token-budget option returns a nonzero status when packed output exceeds the selected limit. It still generates the output file. An automated upload step should therefore honor the exit status rather than treat an existing artifact as evidence that the budget check passed.
For an initial trial, choose one question and the files needed to answer it. Compare the directory listing with the included source, inspect security-scan warnings, and read the output before sharing it. This is a recommended acceptance exercise; the recorded sandbox run did not complete that packing workflow.
MCP access needs an explicit scope
The README says the default MCP server can read any path the host user can access. Its sandbox option confines file tools to a workspace. The supplied extract says sandbox mode refuses paths outside that root, does not load config files, and registers only read-only tools confined to the root. The option description also says remote packing, skill generation and attaching external outputs are disabled.
Choose the workspace deliberately and verify the access behavior required by your deployment. Our recorded run did not reproduce an MCP conversation or perform adversarial access checks. The passing source suite does not establish that a shared agent service is secure.
Configuration can execute commands
The README warns that JavaScript and TypeScript configuration files execute when loaded, processors run external commands, and path options can read outside the repository. Inspect configuration before running Repomix in an unfamiliar checkout.
For remote repositories, the README says configuration is not loaded by default. Opting in can display the config and request confirmation on an interactive terminal. The supplied passage describes saved approval as tied to a hash of the approved config. It does not establish how approval covers imported files or processor scripts, so this review makes no claim about those boundaries.
Repomix also documents Secretlint checks for files matching known credential formats. That content check does not evaluate the commands a configuration will execute. Review configuration and outgoing source separately.
Compare the workflow you need
files-to-prompt accepts files or directories and documents extension filters plus XML and Markdown output. Consider it when those file-collection features cover your task.
Code2Prompt documents Cargo and Homebrew installation, a Python SDK and an MCP server. Consider it when its installation or integration routes fit the surrounding application. Neither alternative was measured in this review.
Documentation scores 4 on this editorial rubric: 1 means absent instructions, 2 partial instructions, 3 a clear basic route, 4 multiple routes with stated limits, and 5 independently verified routes. Repomix's supplied README provides several routes and explains limits such as token-budget exit behavior and remote-config trust. Reading those instructions does not establish that every route works in a supported environment.
The supplied metadata observed on October 28, 2026 records a last push of October 25, 2026. The supplied latest-release record identifies v1.18.1, released September 21, 2026. These dates establish recorded activity, but do not resolve issue health, response quality or deployment reliability. Before adoption, inspect the eight advisories from the measured checkout and decide which files may be shared.