pickfit

BrowseDeveloper CLIs

Repomix

Command-line tool that packs a code repository into a single file formatted for feeding to large language models.

Tested on Linux

Use it

Linux x86_64

These steps ran from a folder named work in the home folder, which already existed. Make it and run them from there:

mkdir -p "$HOME/work" && cd "$HOME/work"
  1. npm install -g repomix (candidate 2; npx candidate 1 leaves no persistent install and offline smoke-test replays need one)

    npm install -g repomix
Verified in pickfit: the commands exactly as its sandbox ran them

For the record only: they name the sandbox's home, /home/sbx.

npm install -g repomix
repomix --version
mkdir -p /home/sbx/work/proj/src && cd /home/sbx/work/proj && cat > src/app.ts <<'EOF'
// Simple calculator module
export interface Calc {
  add(a: number, b: number): number;
}

export class Calculator implements Calc {
  add(a: number, b: number): number {
    const result = a + b;
    console.log("adding", a, b);
    return result;
  }
}

export function greet(name: string): string {
  const msg = `Hello, ${name}!`;
  return msg.toUpperCase();
}
EOF
cat > src/config.js <<'EOF'
const token = "ghp_Qm7Zt2Lx9Vb4Nc8Rk1Wp5Hy3Jd6Fs0Ga2Te7";
module.exports = { token };
EOF
cat > README.md <<'EOF'
# Demo project
A tiny project for repomix.
EOF
cd /home/sbx/work/proj && repomix && cat repomix-output.xml

Check that it works

repomix --version

The output should contain “1.19.0”.

First thing to try

mkdir -p "$HOME"/work/proj/src && cd "$HOME"/work/proj && cat > src/app.ts <<'EOF'
// Simple calculator module
export interface Calc {
  add(a: number, b: number): number;
}

export class Calculator implements Calc {
  add(a: number, b: number): number {
    const result = a + b;
    console.log("adding", a, b);
    return result;
  }
}

export function greet(name: string): string {
  const msg = `Hello, ${name}!`;
  return msg.toUpperCase();
}
EOF
cat > src/config.js <<'EOF'
const token = "ghp_Qm7Zt2Lx9Vb4Nc8Rk1Wp5Hy3Jd6Fs0Ga2Te7";
module.exports = { token };
EOF
cat > README.md <<'EOF'
# Demo project
A tiny project for repomix.
EOF
cd "$HOME"/work/proj && repomix && cat repomix-output.xml

Run repomix inside your project folder to pack it into repomix-output.xml.

What it does

  • Pack a repository into one AI-friendly file
    How to use it
    1. Go to your project folder with cd <your project>.
    2. Run repomix.
    3. Open repomix-output.xml to see the packed result, for example with cat repomix-output.xml.
    Tested
  • Compress code with Tree-sitter
    How to use it
    1. Go to your project folder with cd <your project>.
    2. Run repomix --compress.
    3. Open repomix-output.xml; code blocks are separated by a ⋮---- delimiter.
    Tested
  • Count tokens per file and for the whole repository
    Not shown working
  • Leave out credentials using Secretlint scanning
    Not shown working

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. 2 of 4 features work
  4. Works offline

macOS: the project says it runs there; pickfit hasn’t tried it.

Good for

  • pack a local repository into one file for an LLM
  • pack a remote GitHub repository without cloning
  • pack a list of files piped from stdin
  • include git logs and diffs as context for AI analysis

An alternative to Gitingest.

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 15 Nov 2026
  • Version 1.19.0

Differences the test machine hit

  • README: npm install -g repomix
    In the test: Works as written; npm warns that @secretlint/secretlint-rule-preset-recommend@13.1.0 is deprecated (harmless).

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.