pickfit

BrowseDeveloper CLIs

ci-whisper

Parses failed CI logs to surface the first error, its chain, and a fix.

Tested on Linux

Use it

Linux x86_64

  1. install ci-whisper via pipx git

    pipx install git+https://github.com/mgkvibez/ci-whisper.git

Check that it works

ci-whisper --help

The output should contain “usage: ci-whisper”.

First thing to try

cat > /tmp/build.log <<'LOG'
Starting job: build and test
Run npm ci
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve peer react@"^19" from next@15
##[error]Process completed with exit code 1.
LOG
cp /tmp/build.log ./build.log && cat /tmp/build.log
ci-whisper --file /tmp/build.log

Run ci-whisper --file <file> on a saved CI log, or pipe a log into ci-whisper.

What it does

  • Find the first real error in a CI log
    How to use it
    1. Save the failed job's log to a file.
    2. Run ci-whisper --file <file>.
    3. Look under FIRST REAL ERROR in the output.
    Tested
  • Show the chain of causes behind an error
    How to use it
    1. Run ci-whisper --file <file> --json.
    2. Read the root_cause section of the JSON output.
    Tested
  • Get a suggested fix for a failure
    How to use it
    1. Pipe the log into the tool with cat <file> | ci-whisper.
    2. Read the SUGGESTED FIX section of the output.
    Tested

How far pickfit got

Linux x86_64

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

Good for

  • summarize a failing GitHub Actions job log via pipe
  • analyze a downloaded build log file
  • output log analysis as machine-readable JSON

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

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.