Zum Hauptinhalt springen
tsecurity.de LIVE
Echtzeit-Radar & Feeds
Alle RSS Feeds
👥 Community & Social
Windows Tipps & SecurityGoogles neues Betriebssystem ist da – heißt jetzt aber komplett anders(22.09.2026 um 12:08 Uhr)
Windows Tipps & SecurityGooglebook-Premiere: Alle 5 Modelle ausprobiert – zwei stechen heraus(22.09.2026 um 12:30 Uhr)
Sichere ProgrammierungDeprecation notice: All-platform CodeQL bundle(22.09.2026 um 11:21 Uhr)
Sichere ProgrammierungCodeSOD: The John Cage Variable(22.09.2026 um 08:30 Uhr)
Windows Tipps & SecurityGoogles neues Betriebssystem ist da – heißt jetzt aber komplett anders(22.09.2026 um 12:08 Uhr)
Windows Tipps & SecurityGooglebook-Premiere: Alle 5 Modelle ausprobiert – zwei stechen heraus(22.09.2026 um 12:30 Uhr)
Sichere ProgrammierungDeprecation notice: All-platform CodeQL bundle(22.09.2026 um 11:21 Uhr)
Sichere ProgrammierungCodeSOD: The John Cage Variable(22.09.2026 um 08:30 Uhr)
Intelligence View
⚡ tsecurity.de Intelligence

I built a CLI that reads your broken CI log and tells you why it failed in plain English

Every developer knows the feeling. Your CI pipeline fails. You open the log. There are 300 lines of noise — progress bars, timestamps, test runner output — and somewhere buried in there is the one line that actually matters. I got tired o…

0
↗ Quelle (dev.to)
Reagiere als Erste:r — dein Feedback zählt!

Every developer knows the feeling.



Your CI pipeline fails. You open the log. There are 300 lines of noise — progress bars, timestamps, test runner output — and somewhere buried in there is the one line that actually matters.



I got tired of hunting for it. So I built ci-why.






What it does



You pipe your failed CI log into it, and it tells you:





  • WHY the build failed (in one sentence)


  • Which exact line caused it


  • What to fix




cat build.log | ci-why






That's it. You get back something like this:




──────────────────────────────────────────────────
WHY
The authentication service is returning null for the token field
instead of a valid token string, causing the test assertion to fail.

FAILING LINE
src/services/auth.test.ts:63

SUGGESTED FIX
Check authService.login() in auth.ts — it's returning {"token": null}
for valid credentials. The login logic needs fixing, not the test.
──────────────────────────────────────────────────






Instead of reading 300 lines, you read 8.






How to install it






npm install -g ci-why






You'll need an Anthropic API key (free to get at console.anthropic.com). Set it once:




export ANTHROPIC_API_KEY=your-key-here






Then use it however fits your workflow:




# Pipe from anywhere
cat build.log | ci-why

# Point at a file
ci-why ./logs/build.log









How it works



ci-why does four things under the hood:





  1. Strips the noise — removes ANSI escape codes, progress bars, timestamps, and anything else that clutters CI logs


  2. Finds the signal — pulls out lines containing errors, exceptions, and failures, plus the last section of the log


  3. Asks Claude — sends the cleaned excerpt to the Anthropic API with a tight prompt asking for: why, where, and how to fix it


  4. Prints the result — formats it into the clean coloured output you saw above



The whole thing uses claude-haiku which is fast and cheap. A typical analysis costs less than a fraction of a cent.






It's free and open source



ci-why is completely free. You bring your own Anthropic API key so there's no subscription, no account, no billing through me.



The code is on GitHub: github.com/ciwhy-tool/ci-why



A paid cloud tier with GitHub Actions integration and team features is planned for the future — but the core CLI will always be free and open source.






What's coming next




  • GitHub Actions integration (auto-comment on PRs with the failure explanation)

  • Support for more log formats (pytest, Go test, Cargo, Maven)


  • --json flag for piping output into other tools






Try it and let me know what you think



If you try ci-why and hit a bug, have a suggestion, or just want to say it helped — drop a comment below or open an issue on GitHub. This is v0.1 and real feedback from real developers is exactly what I need to make it better.




npm install -g ci-why


Ähnliche Beiträge
🔍 Verwandte News

Auch interessante Nachrichten I built a CLI that reads your broken CI log and tells you why it failed in plain English

Thematisch verwandte Begriffe: built, that, reads, your · 6 Treffer

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Zum Aktualisieren ziehen
ZERO-DAY CVE-2026-94493 | A vulnerability was detected in Gigatech PDV5701 1.0.31_240305_112640. T…
Advisory →
TTS Reader • tsecurity.de Voice
tsecurity.de Icon
tsecurity.de App
Offline-Lesen, Eilmeldungen & 0ms Ladezeit

Installiere tsecurity.de direkt auf deinen Home-Bildschirm für das ultimative Vollbild-Magazinerlebnis ohne Browser-Leisten.

Nächster Beitrag
Themen-Radar & Intelligence Matrix
Echtzeit-Taxonomie nach Angriffsvektoren & Plattformen

tsecurity.de Live Threat Radar

🔴 LIVE RADAR
MONITORING
AKTIV
CVE-DATENBANK
LIVE
🔍
Community Radar & Live Chat
Sentinel Bot online • Live-Stream
Dein Cluster: Security Explorer
Match:
lädt…
Verbindung zum Community-Stream wird aufgebaut...
Bearbeitungsmodus — Senden überschreibt deine Nachricht
Community-Puls — was gerade passiert
lädt…
Aktivitäten deiner Analysten
lädt…
Neues Thema oder Eilmeldung einreichen

Reiche interessante Links, Zero-Days oder Debatten ein. Die Community entscheidet per Upvote über die Veröffentlichung.

Heiß diskutierte Einreichungen
🔖 Gespeicherte Artikel
📂 Keine gespeicherten Artikel vorhanden.
Zurück Ziehen Vor
Links: vorheriger Artikel Rechts: nächster Artikel unten: schließen
News NIS-2 Frühwarnung Tier-1 Intel ⏱️ 3 Min vor 10 Min
Artikeldaten werden geladen...

Zurück: vorheriger Vor: nächster
↗ Original-Quelle
Social Reaktionen Deine Reaktion zählt
Einstufung & Relevanz-Poll 0 Stimmen
In sozialen Netzwerken teilen 1-Klick