What the tool does.
PatchRail reads a failing CI log and answers the first triage question — which subsystem broke — before you spend a morning bisecting your own code.
31 failure classes
A raw CI log is matched against the failure classes that actually show up in red builds — OOM-killed runners, transient network errors, lockfile drift, flaky tests, expired credentials, and more. Each match names the class and the literal signature line that triggered it.
Redaction before anything else
Tokens, credentialed URLs, and obvious secrets are stripped from the log before classification and before any output is written. The summary tells you what was redacted.
Fully offline
Local rules, no network calls, no account, no telemetry. Your logs never leave the machine — which is the point when the log is the thing that leaks.
CLI or CI step
Run it by hand on a downloaded log, or add the PatchRail Action so failed GitHub Actions builds are annotated with the matching failure guide automatically.
Open source, all of it.
The CLI, the classification rules, and the 31 fix playbooks are Apache-2.0. There is no paid tier and nothing held back — the failure guides behind every class are published free on this site.
pipx install patchrail