ci-whisper
Parses failed CI logs to surface the first error, its chain, and a fix.
Tested on Linux
Use it
Linux x86_64
install ci-whisper via pipx git
pipx install git+https://github.com/mgkvibez/ci-whisper.git
Check that it works
ci-whisper --helpThe 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.logci-whisper --file /tmp/build.logRun 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 logTested
How to use it
- Save the failed job's log to a file.
- Run
ci-whisper --file <file>. - Look under FIRST REAL ERROR in the output.
- Show the chain of causes behind an errorTested
How to use it
- Run
ci-whisper --file <file> --json. - Read the
root_causesection of the JSON output.
- Run
- Get a suggested fix for a failureTested
How to use it
- Pipe the log into the tool with
cat <file> | ci-whisper. - Read the SUGGESTED FIX section of the output.
- Pipe the log into the tool with
How far pickfit got
Linux x86_64
- Installs
- Starts
- 3 of 3 features work
- 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