dosa.dev logo Workflow guides

Workflow guide · 3 tools

How to triage CI failures with AI

When a pipeline goes red, start by finding the first actionable error. A broken dependency install, a flaky test and an actual regression can all end with the same exit code, but they call for different fixes.

Compare the tools

Tool Best for Tradeoff
GitHub MCP Server Bringing GitHub Actions run history and build failures into an MCP-capable assistant. Requires an MCP client and GitHub credentials. It can fetch run evidence but does not mirror the runner locally.
Claude Code Reproducing a shell command or failing test in a local checkout. Your shell is not the hosted runner. Differences in OS, permissions or service containers can hide the failure.
GitHub Copilot Investigating a test or workflow change without leaving your editor. Editor context alone may miss matrix configuration, run logs and external service failures.

A practical workflow

  1. Capture the failing job and step, commit SHA, runner image and first useful error. Remove secrets before sharing logs with any model.
  2. Compare with the last green run. Check for changes in dependencies, runner images and environment before blaming the code diff.
  3. Reproduce with the same command and versions where possible. Verify the smallest fix on the same CI job rather than treating a successful retry as proof.

Try one on your project

  • GitHub MCP Server

    Give your client read-only access and have it compare the failed job with the last passing run. Ask it to cite the workflow, run and step behind each finding.

  • Claude Code

    Supply the sanitized error and exact failing command. Ask for a reproduction before allowing code edits.

  • GitHub Copilot

    Open the workflow and changed source files together. Share the failing matrix entry and ask which local check would separate a CI setup issue from a regression.

← All workflow guides