pickfit

BrowseDeveloper CLIs

fzf

General-purpose command-line fuzzy finder for interactively filtering and selecting items.

Tested on Linux

Use it

Linux x86_64

  1. git clone fzf repo

    git clone --depth 1 https://github.com/junegunn/fzf.git ~/.fzf
  2. download binary via install --bin

    ~/.fzf/install --bin 2>&1
    ~/.fzf/bin/fzf --version
  3. link binary to ~/.local/bin for PATH

    mkdir -p ~/.local/bin && ln -sf ~/.fzf/bin/fzf ~/.local/bin/fzf
    export PATH="$HOME/.local/bin:$PATH"
    fzf --help

Check that it works

fzf --version

The output should contain “0.74.5”.

First thing to try

mkdir -p /tmp/fzfsel && echo "hello" > /tmp/fzfsel/file1.txt && echo "world" > /tmp/fzfsel/file2.txt && cd /tmp/fzfsel && find . -type f | fzf --filter="file1" > /tmp/fzf_test/selected.txt && cat /tmp/fzf_test/selected.txt

What it does

  • Select files with fuzzy matching
    Tested
  • Browse command history interactively
    Not tested
  • Preview items in preview window
    Not shown working
  • Fuzzy complete files and commands
    Not tested

How far pickfit got

Linux x86_64

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

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.74.5

Differences the test machine hit

  • README: git clone then ~/.fzf/install builds from source
    In the test: install script downloads prebuilt binary without Go; use --bin to avoid interactive prompts
  • README: sudo apt install fzf for Debian
    In the test: no root/sudo in box, binary download method required

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.