Paste a failing CI log and get a plain-English diagnosis — dependency conflict, flaky test, build error, race condition, or environment issue.
CI failures produce walls of text. Finding the root cause usually means scanning hundreds of log lines for the one error that matters. badgr-ci-triage classifies the failure instantly and tells you exactly what to do — no log reading required.
Accepts log text via --log or piped stdin, so it drops straight into an existing CI failure step.
Matches known patterns — ERESOLVE, tsc/SyntaxError, snapshot mismatches, deploy timeouts, missing env vars — into one of six categories.
Prints the category, the matched error line, and a concrete recommended action, with exit code 0 once categorized or 1 if the log was empty or unrecognized.
npx badgr-ci-triage --log "npm ERR ERESOLVE unable to resolve dependency tree"Requires Node.js 18+.
Pass log text directly, or pipe it from a file or CI step. Add --json for structured output in dashboards.
cat ci-output.txt | npx badgr-ci-triage
npx badgr-ci-triage --log "TypeError: Cannot read properties of undefined" --jsonbadgr-ci-triage — dependency failure
✗ ERESOLVE: unable to resolve dependency tree
Recommended action: Delete node_modules and package-lock.json, then reinstall from scratch.
rm -rf node_modules package-lock.json && npm installnpx badgr-ci-triage --log "npm ERR ERESOLVE unable to resolve dependency tree" — no account needed to get started.