pickfit

BrowseDeveloper CLIs

Eckra

AI-powered Git tool that writes commit messages and manages staging, branches, and remotes in one dashboard.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: Node.js 22.13 or newer
  1. Install eckra via npm global

    npm install -g eckra
Where the README and reality differ
  • README: No config required to get started; eckra status shows status
    What worked: eckra status first launches interactive setup wizard (Which AI provider...) and hangs without a TTY; eckra doctor --no-provider works offline without onboarding

Check that it works

eckra --version

The output should contain “1.6.1”.

First thing to try

mkdir -p /tmp/eckra-test && cd /tmp/eckra-test && git init -q 2>&1; git config user.email "test@test.com" && git config user.name "Test" && echo "hello" > hello.txt && git add hello.txt && git commit -qm "initial commit" && echo "world" >> hello.txt && git log --oneline | head -n 5 && pwd
cd /tmp/eckra-test && eckra doctor --no-provider

Open a terminal in a Git repository and run eckra doctor --no-provider to check your setup.

What it does

  • Write commit messages from your changes with AI
    Not tested
  • Manage staging, branches, stashes and remotes
    Not tested
  • Build an AI timeline of your commit history
    Not tested
  • Browse an interactive commit graph across branches
    Not tested

How far pickfit got

Linux x86_64

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

Good for

  • generate AI-assisted commit message from diff
  • view status and staged files
  • generate AI project timeline from commit history
  • browse interactive commit graph across branches
  • print release notes since last tag

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 1.6.1

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.