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 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: ──────────