ci-whisper
Read a failed CI log. Get the first real error, its causal chain, and a fix. One paragraph instead of ten thousand lines of noise.
Install
pipx install git+https://github.com/mgkvibez/ci-whisper.git
Until it is on PyPI, install from git. For development: git clone && pip install -e ".[dev]".
Three ways to use it
# 1. The one you will use daily: pipe the failing job log
gh run view --log-failed | ci-whisper
# 2. From a downloaded log file
ci-whisper --file /tmp/build.log
# 3. Let it fetch the last failed run of the current repo
ci-whisper --gh 16977481234
# machine-readable, for a bot or an agent skill
ci-whisper --file build.log --json
Exit code is 1 when no error signal is found, so you can gate on it.
Why it exists
A red build hands you 10k lines. The actual cause is line 4, and everything after it is consequence: retries, cascading test failures, the polite ##[error]Process completed with exit code 1.
Two things go wrong when this hits an agent. It reads the last error and fixes a symptom, or it reads the header and summarises nothing. ci-whisper ranks signals so the cause outranks its own consequences, then shows the citations so anyone can check the call.
How it works
- Clean — strips ANSI and GitHub's
2026-10-29T08:01:02.1234567Ztimestamp prefix, keeping a line-number map to the original file. - Scan — matches a ranked rule set:
ModuleNotFoundError/Exception(4) beatTraceback, test failures and compiler errors (3), which beatnpm ERR!and##[error](2), which beat a bareexit code 1(1). - Root cause — highest severity, then earliest line. Noise (warnings, deprecations,
0 failed, download progress) is filtered before ranking. - Chain — the chosen line plus the following block: indented continuations, frames, and
caused bystyle links. - Fix — a rule per failure shape: peer dependency conflict, missing module, permissions, missing path, assertion, timeout, OOM.
No network calls, no LLM, no dependencies.
Contributing
Read CONTRIBUTING.md. Tests:
python -m pytest -q
License
MIT. See LICENSE.
Metadata
Release files for ci-whisper 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ci_whisper-0.1.2.tar.gz | 10.0 kB | With provenance | Details for ci_whisper-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ci_whisper-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for ci_whisper-0.1.2-py3-none-any.whl |
Total release size: 19.9 kB
Release files / ci_whisper-0.1.2.tar.gz
| Download URL | ci_whisper-0.1.2.tar.gz |
|---|---|
| Size | 10.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
24f70a0d36b42522e66ccc923b858360c374bdda93c77b664bf2061b32687357
|
|
BLAKE2b-256 checksum How to use checksums |
b13e78c12f304f6697b3447083b3201cf86d3674c871cb40b096b6d9ac331dd8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.
Transparency logRelease files / ci_whisper-0.1.2-py3-none-any.whl
| Download URL | ci_whisper-0.1.2-py3-none-any.whl |
|---|---|
| Size | 9.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
69a421fd5df467f022e196f8e759631ab09012b143ff64d7d69b6ef16289f72f
|
|
BLAKE2b-256 checksum How to use checksums |
5710d7ab49a40b283182954973361cd0c00d7ec408a13d8837c10be4b0298384
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.
Transparency logSecurity for ci-whisper 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for ci_whisper-0.1.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.