Tool roles, alternatives, selection tradeoffs, and compatibility caveats.
AI context bundlers (repo → prompt)
John uses: packx (npm install -g packx, johnlindquist on npm) — filters repository files by content string and extension before bundling for AI consumption, with saved search configs. Section 08's oracle skill uses it to bundle up to ~900k tokens per consult. (Related: johnlindquist/pack, a content-filter front-end for Repomix.)
| Alternative | What it is | How it differs | License |
|---|---|---|---|
| Repomix | Packs an entire repository into a single AI-friendly file (XML/MD), with token counts and remote-repo support | Whole-repo packing with include/exclude globs; packx's content-string filtering is the main thing it lacks (John's `pack` wraps Repomix to add it) | MIT |
| gitingest | Replace 'hub' with 'ingest' in any GitHub URL to get a prompt-friendly extract | Zero-install for public repos (URL trick + web UI); also a pip CLI | MIT |
| code2prompt | Rust CLI: codebase → single prompt with source tree, Handlebars templating, token counting | Template-driven output shaping; closest feature set to packx minus content search | MIT |
| files-to-prompt | Simon Willison's minimal concatenator: directory → one prompt (pairs with his `llm` CLI) | Deliberately tiny; no filtering logic beyond paths; check current repository activity (stable, not active) | Apache-2.0 |
| yek | Fast Rust serializer for repo files, chunks by token budget, priority-orders files | Speed and token-budget chunking focus; good for very large repos | MIT |
Pick this if…
- Repomix — the default choice; the biggest, most maintained repo-packer. packx's content-search filtering is the one thing you'll miss.
- gitingest — you mostly bundle public repos and want zero install.
- code2prompt — you want templated output shaping (Handlebars) around the bundle.
- files-to-prompt — you want the smallest possible tool, especially with
llm(stable but not actively developed). - yek — your repos are huge and you need token-budget chunking fast.