pickfit

BrowseDeveloper CLIs

lazygit

Terminal UI for performing git commands interactively.

Tested on Linux

Use it

Linux x86_64

  1. Install lazygit binary from GitHub releases

    mkdir -p ~/.local/bin && curl -fsSL -o /tmp/lazygit.tar.gz https://github.com/jesseduffield/lazygit/releases/download/v0.66.2/lazygit_0.66.2_linux_x86_64.tar.gz && tar -xzf /tmp/lazygit.tar.gz -C /tmp && mv /tmp/lazygit ~/.local/bin/lazygit && chmod +x ~/.local/bin/lazygit && ~/.local/bin/lazygit --version

Check that it works

lazygit --version

The output should contain “version=0.66.2”.

First thing to try

cat <<'EOS' >/tmp/setup_lz.sh
#!/bin/bash
set -e
# F1 repo with hunks
rm -rf /tmp/lz_f1 /tmp/lz_f2 /tmp/lz_f3 /tmp/lz_f4
mkdir -p /tmp/lz_f1 && cd /tmp/lz_f1 && git init -q && git config user.email "a@a.com" && git config user.name "a" && echo -e "line1\nline2\nline3\nline4" > file.txt && git add . && git commit -qm "init" && echo -e "line1\nchanged2\nline3\nchanged4" > file.txt
# F2 repo for rebase
mkdir -p /tmp/lz_f2 && cd /tmp/lz_f2 && git init -q && git config user.email "a@a.com" && git config user.name "a" && echo "a" > f.txt && git add . && git commit -qm "c1" && echo "b" >> f.txt && git add . && git commit -qm "c2"
# F3 repo for cherry-pick
mkdir -p /tmp/lz_f3 && cd /tmp/lz_f3 && git init -q && git config user.email "a@a.com" && git config user.name "a" && echo "a" > f.txt && git add . && git commit -qm "c1" && git checkout -qb feature && echo "feature" > feat.txt && git add . && git commit -qm "feat" && git checkout -q master
# F4 repo for bisect
mkdir -p /tmp/lz_f4 && cd /tmp/lz_f4 && git init -q && git config user.email "a@a.com" && git config user.name "a" && echo "a" > f.txt && git add . && git commit -qm "c1" && echo "b" >> f.txt && git add . && git commit -qm "c2" && echo "c" >> f.txt && git add . && git commit -qm "c3" && git bisect start >&/dev/null && git bisect bad HEAD >&/dev/null; git bisect good HEAD~2 >&/dev/null || true
echo "setup done"
EOS
chmod +x /tmp/setup_lz.sh
/tmp/setup_lz.sh
echo "F1 check:" && cd /tmp/lz_f1 && git diff --stat && lazygit --config | grep -q toggleStagedAll && echo "F1_stage_feature_present"

What it does

  • Stage hunks or individual lines
    Not shown working
  • Perform interactive rebase
    Not shown working
  • Cherry-pick commits
    Not shown working
  • Bisect commits to find bug
    Not tested

How far pickfit got

Linux x86_64

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

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

Good for

  • stage hunks or individual lines
  • do interactive rebase of commits
  • cherry-pick commits
  • bisect commits to find regression
  • reset dirty working tree

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 4 Nov 2026
  • Version 0.66.2

Differences the test machine hit

  • README: sudo xbps-install -S lazygit
    In the test: Download linux_x86_64 tarball from GitHub releases and install to ~/.local/bin (no sudo in box)

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.