How I Built an AI That Diagnoses GitHub Actions Failures Automatically

The Problem GitHub Actions failure logs are noisy. Finding the actual error in 500 lines of output takes time you don't have during an incident. You get a red X, click through multiple pages, scroll past runner setup noise and dependency install output, land on the real error — and then you have to figure out what it means and what to do about it. I was doing this loop manually too often, so I automated it. What It Does The tool fetches your repository's failed workflow runs via the GitHub API, extracts the relevant error sections from job logs, pulls in the workflow YAML for context, and sends everything to Ollama running locally. You get back a root cause, an explanation of why it happened, exact YAML changes to make, and steps to prevent it from happening again — in about 15 seconds. Zero cloud costs. Your logs and code never leave your machine. The 5 Failure Types It Handles Dependency conflicts — version mismatches, packages missing from requirements.txt or package.json Missing se