pickfit

BrowseDeveloper CLIs

mergegate

Local hub to review AI agent code branches in one prioritized inbox.

Tested on macOS and LinuxKnown vulnerabilities

Use it

Before you install: known vulnerabilities

pickfit found 4 known high or critical vulnerabilities in the packages a fresh install brings (OSV.dev, 3 Nov 2026). Weigh this before you install it.

  • crates:wasmtime 48.0.6 Wasmtime: Cranelift backend on aarch64 can jump to incorrect target on large Wasm `br_table` instruction (GHSA-mghf-wjfp-p5xm, critical, fixed in 48.0.7)
  • npm:dompurify 3.4.16 DOMPurify SAFE_FOR_TEMPLATES bypass: split template expressions survive in attached shadow root content on DOM output modes (GHSA-cg2g-xh64-v4q7, critical, fixed in 3.4.17)
See 2 more

macOS arm64

You need first

  • System packages: git 2.40 or newer, GitHub CLI (gh)
  1. Install mergegate via mise packslip

    mise use -g packslip:damian-kolasinski/mergegate
  2. Symlink mg/mergegate into ~/.local/bin so they are on PATH

    ln -sf "$HOME"/.local/share/mise/installs/packslip-damian-kolasinski-mergegate/0.11.0/mg "$HOME"/.local/bin/mg && ln -sf "$HOME"/.local/share/mise/installs/packslip-damian-kolasinski-mergegate/0.11.0/mg "$HOME"/.local/bin/mergegate && ls -l "$HOME"/.local/bin/mg* && mg --version && mergegate --version
Where the README and reality differ
  • README: mg skill status shows what's installed
    What worked: mg skill has only subcommand `install` (plus --help); `mg skill status` returns error unrecognized subcommand 'status'
Verified in pickfit: the commands exactly as its sandbox ran them

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

mise use -g packslip:damian-kolasinski/mergegate 2>&1
ln -sf /Users/sbx/.local/share/mise/installs/packslip-damian-kolasinski-mergegate/0.11.0/mg /Users/sbx/.local/bin/mg && ln -sf /Users/sbx/.local/share/mise/installs/packslip-damian-kolasinski-mergegate/0.11.0/mg /Users/sbx/.local/bin/mergegate && ls -l /Users/sbx/.local/bin/mg* && mg --version && mergegate --version
mg --version
mg doctor 2>&1

Check that it works

mg --version

The output should contain “mg 0.11.0”.

First thing to try

mg doctor 2>&1

Run mg doctor first to check your setup.

Linux x86_64

You need first

  • System packages: git 2.40 or newer, GitHub CLI (gh)
  1. Download mise install script

    curl -fsSL https://mise.run -o /tmp/mise-install.sh
  2. Install mise to ~/.local/bin

    sh /tmp/mise-install.sh 2>&1 && ~/.local/bin/mise --version
  3. Install mergegate via mise packslip

    export PATH="$HOME/.local/bin:$PATH" && mise use -g packslip:damian-kolasinski/mergegate
  4. Link mg onto default PATH and verify

    ln -sf "$HOME/.local/share/mise/installs/packslip-damian-kolasinski-mergegate/0.11.0/mg" "$HOME/.local/bin/mg" && ln -sf "$HOME/.local/bin/mg" "$HOME/.local/bin/mergegate" && mergegate --version
Where the README and reality differ
  • README: mg skill status shows what's installed (and mg skill setup / mg skill remove exist)
    What worked: mg skill has only the 'install' subcommand; 'status', 'setup' and 'remove' from the README are rejected as unrecognized (exit 64)

Check that it works

ln -sf "$HOME/.local/share/mise/installs/packslip-damian-kolasinski-mergegate/0.11.0/mg" "$HOME/.local/bin/mg" && ln -sf "$HOME/.local/bin/mg" "$HOME/.local/bin/mergegate" && ls -l ~/.local/bin/mg ~/.local/bin/mergegate && mg --version && mergegate --version

The output should contain “mg 0.11.0”.

First thing to try

mg doctor

Run mg doctor first to check your setup.

What it does

  • Review all agents' work in one inbox
    Not tested
  • Review files ordered by importance
    Not tested
  • Send feedback back to agents
    Not tested
  • Approve items to squash-merge them
    Not tested

How far pickfit got

macOS arm64

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

Linux x86_64

  1. Installs
  2. Starts
  3. Main function works
  4. Works offline

Good for

  • Submit current branch for review as a new revision
  • Wait for review feedback on an item
  • Squash-merge an approved item

An alternative to GitHub web UI.

How pickfit tested it

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

macOS arm64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 1 Nov 2026
  • Version 0.11.0

Differences the test machine hit

  • README: mise use -g packslip:damian-kolasinski/mergegate installs mg on PATH
    In the test: mise installs binary to .local/share/mise/installs/.../latest/.mise-bins which is only on PATH via `mise env`; manual symlink to ~/.local/bin required for plain PATH
  • README: macOS ships /usr/bin/mg conflicts; install also provides `mergegate` alias
    In the test: `mergegate` binary only available via mise shim; same symlink needed as for mg

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 30 Oct 2026
  • Version 0.11.0

Differences the test machine hit

  • README: mise use -g packslip:damian-kolasinski/mergegate
    In the test: Installed mise first with the script from https://mise.run to ~/.local/bin/mise, then ran the README's mise command
  • README: mise install puts mg on your PATH
    In the test: Symlinked the mise-installed mg binary into ~/.local/bin (plus a mergegate alias) because mise's shims dir is not on this box's default PATH
  • README: Install script contents as read before running
    In the test: The mise installer downloads a prebuilt mise binary at run time; integrity is enforced by the script's embedded checksum check

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.