Repomix

Pick Repomix when the problem is context, not intelligence. If you already pay for Claude, ChatGPT, Gemini, or Grok and want the model to see the full project instead of the three files you remembered to paste, one command gets you there. We'd reach for it before a code review, a refactor pass, or a dependency security check where the model needs the shape of the whole repo. The token accounting is what makes it usable on real projects rather than toy ones. Per-file and repo-wide counts tell you upfront whether the pack fits, and Tree-sitter compression (roughly 70% token reduction by the vendor's measure) buys room when it doesn't. Strip comments and empty lines separately if you want more. Pass when your monorepo is so big that even a compressed pack blows past the window — Repomix won't make that math work, and you're better off scoping hard with `--include` or feeding files selectively. Non-developers who won't touch a terminal or Node install should look at the Chrome extension first. And if you want a tool that edits your code rather than describes it, this isn't it; there's no model inside. Where it bites: Secretlint catches files matching known credential formats, not every secret that happens to live in a config file, so review the pack before it leaves your machine. The learning curve is real if globs and flags feel foreign, though `repomix --init` and the config file smooth repeat runs. Against Aider's repo map or a homemade `find | xargs cat` script, Repomix wins on hygiene — gitignore rules, credential screening, token counts, multiple output formats — and it costs nothing under MIT. The MCP Server and GitHub Actions workflow mean it's not just a manual CLI habit; you can automate snapshots into CI or wire it into an AI assistant. My take: keep