pickfit

BrowseDeveloper CLIs

aic

Turns a messy git working tree into atomic conventional commits using AI.

Tested on Linux

Use it

Linux x86_64

  1. download installer script

    curl --proto '=https' --tlsv1.2 -sSfL https://github.com/CaicoLeung/aic/releases/latest/download/aic-installer.sh -o /tmp/aic-installer2.sh
  2. run installer script

    sh /tmp/aic-installer2.sh
  3. put aic on PATH via ~/.local/bin symlink

    mkdir -p ~/.local/bin && ln -sf ~/.cargo/bin/aic ~/.local/bin/aic

Check that it works

aic --version

The output should contain “aic 0.6.1”.

First thing to try

aic list

Run aic list inside a git repository to get started.

What it does

  • Split a messy working tree into atomic commits
    Not tested
  • Write commit messages in Conventional Commits style
    Not tested
  • Resolve git merge conflicts
    Not tested
  • Undo the commits from the last run
    Not tested

How far pickfit got

Linux x86_64

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

Good for

  • split unstaged changes into atomic commits
  • resolve git merge conflicts via LLM
  • undo last run and restore changes unstaged

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 30 Oct 2026
  • Version 0.6.1

Differences the test machine hit

  • README: curl ... aic-installer.sh | sh installs aic
    In the test: installer places binary in ~/.cargo/bin; symlinked it to ~/.local/bin which is on PATH
  • README: aic completion installs shell completions
    In the test: run with SHELL=/bin/bash (e.g. SHELL=/bin/bash aic completion); bare call fails when $SHELL is unset
  • README: aic-installer.sh installer script
    In the test: installer fetches prebuilt binary tarball (e.g. aic-x86_64-unknown-linux-gnu.tar.gz) which cannot be read as text
  • README: install step 2 runs aic-installer2.sh
    In the test: nothing to change; a note: the box ran aic-installer2.sh, downloaded, without reading it first, so pickfit did not inspect it

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.