pickfit

BrowseDeveloper CLIs

drydock

TUI dashboard that shows uncommitted, unpushed and unreleased state across many git repositories.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: rust
  • System packages: git
  1. download drydock-linux-x86_64 v1.3.1 and install to ~/.local/bin

    curl -fsSL https://github.com/yetidevworks/drydock/releases/download/v1.3.1/drydock-linux-x86_64.tar.gz -o /tmp/drydock.tar.gz && mkdir -p ~/.local/bin && tar -xzf /tmp/drydock.tar.gz -C /tmp && find /tmp -maxdepth 2 -name drydock -type f -exec cp {} ~/.local/bin/drydock \; && chmod +x ~/.local/bin/drydock && ~/.local/bin/drydock --version

Check that it works

drydock --version

The output should contain “drydock 1.3.1”.

First thing to try

cat <<'EOS' > /tmp/setup_repos.sh
#!/bin/bash
set -e
rm -rf /tmp/fleet
mkdir -p /tmp/fleet/group1
# repo1: with remote and unpushed commits
mkdir -p /tmp/remote.git
git init --bare /tmp/remote.git -q

# repoA: clone, make commits, create side branch with unpushed
git clone /tmp/remote.git /tmp/fleet/group1/repoA -q
git -C /tmp/fleet/group1/repoA config user.email "test@test.com"
git -C /tmp/fleet/group1/repoA config user.name "test"
echo "hello" > /tmp/fleet/group1/repoA/file.txt
git -C /tmp/fleet/group1/repoA add . && git -C /tmp/fleet/group1/repoA commit -qm "initial"
git -C /tmp/fleet/group1/repoA push -q origin HEAD
# unpushed commit on main
echo "more" >> /tmp/fleet/group1/repoA/file.txt
git -C /tmp/fleet/group1/repoA commit -am "unpushed main" -q
# side branch with unpushed
git -C /tmp/fleet/group1/repoA checkout -b feature -q
echo "feature" > /tmp/fleet/group1/repoA/feature.txt
git -C /tmp/fleet/group1/repoA add . && git -C /tmp/fleet/group1/repoA commit -qm "feature work"
git -C /tmp/fleet/group1/repoA checkout master -q 2>&1 || git -C /tmp/fleet/group1/repoA checkout main -q

# repoB: clean repo
git clone /tmp/remote.git /tmp/fleet/group1/repoB -q
git -C /tmp/fleet/group1/repoB config user.email "test@test.com"
git -C /tmp/fleet/group1/repoB config user.name "test"
echo "repoB" > /tmp/fleet/group1/repoB/readme.txt
git -C /tmp/fleet/group1/repoB add . && git -C /tmp/fleet/group1/repoB commit -qm "repoB init"
echo done
EOS
chmod +x /tmp/setup_repos.sh
/tmp/setup_repos.sh
ls /tmp/fleet/group1/repoA/.git -d
git -C /tmp/fleet/group1/repoA log --all --oneline --graph
drydock list --root /tmp/fleet --json > /tmp/out2.json && cat /tmp/out2.json

What it does

  • Show unpushed commits across every local branch
    Tested
  • Browse live TUI table with filters, fuzzy search and detail history view
    Not tested

How far pickfit got

Linux x86_64

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

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

Good for

  • view uncommitted and unpushed changes across all owned repos
  • filter repos touched recently and find work worth releasing

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 2 Nov 2026
  • Version 1.3.1

Differences the test machine hit

  • README: cargo install drydock or make install from source (requires Rust)
    In the test: used prebuilt linux-x86_64 tarball from GitHub releases; no Rust toolchain needed

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.