🩺 CI Doctor

Diagnose the failure before editing CI

CI Doctor turns a failed pipeline into one evidence-backed diagnosis, a bounded fix, and a clear approval boundary. It starts with GitHub Actions and recognizes GitLab CI and CircleCI markers from supplied configuration and logs.

Handles failures with no steps or logs

When a job exposes no normal steps or an empty steps array, CI Doctor does not guess that application code or a secret failed. It inspects run and job state, annotations, the workflow at the failing commit, runner assignment and labels, environment protections, job conditions and dependencies, reusable workflows, and matrix siblings. If the evidence remains incomplete, it reports an unresolved pre-step failure and names the next read-only check.

Understands matrix behavior

CI Doctor traces fail-fast cancellations back to the earliest required sibling failure and distinguishes job-level allowed failures from step-level continue-on-error behavior. It preserves intentional experimental jobs rather than turning required failures green.

Evidence first, mutations by approval

• Inspects workflow YAML, manifests, lockfiles, tests, diffs, logs, and run metadata.
• Separates the primary cause from cascading errors and cancelled matrix siblings.
• Returns run state, root cause or explicit uncertainty, short evidence, the smallest fix or next check, and confidence and unknowns.
• Never treats a secret reference or empty step list as proof that a secret is missing.
• Asks before editing files, rerunning CI, setting secrets, committing, pushing, or opening a pull request.