Skip to main content
Bring the CI Failure Fixer pattern to CircleCI. When a CircleCI workflow fails on a pull request, this automation fires a Devin session with full pipeline context — Devin uses the CircleCI MCP to pull the job logs, test reports, and artifact output, then pushes a targeted fix commit to the same branch.

Use this template

Open CircleCI Failure Fix in Devin and create the automation with the default configuration. You can customize it before saving.

​
What this automation does

The CircleCI MCP gives Devin deep integration with your CI — not just the pass/fail status, but the full log stream, test results, artifacts, and config. That’s the difference between “a test failed” and “this assertion at line 47 failed because the expected string changed last week.” Devin uses that context to ship fixes that actually work the first time.

​
How it works

Trigger: Github event — check.run
  • Event: github:check_run
    • Conditions:
      • action eq completed
      • check_run.conclusion eq failure
      • check_run.name contains circleci
      • repository.full_name eq your-org/your-repo
What Devin does: Starts a session with full event context, executes the prompt below, and (optionally) notifies you on failure.

​
Prerequisites

​
Example prompt

The template ships with this prompt. You can edit it after clicking Use template, or leave it as-is.

​
Setting it up

  1. Open Automations → Templates in Devin.
  2. Click CircleCI Failure Fix. The create page opens with this template pre-filled.
  3. Connect any required integrations and install MCP servers if you haven’t already.
  4. Replace any placeholder values in the trigger conditions (for example, swap your-org/your-repo for your actual repo).
  5. Review the prompt and adjust it for your team’s language, conventions, and guardrails.
  6. Click Create automation.
Most automation templates include suggested ACU and invocation limits to bound cost during early rollout. Keep them as-is until you’re confident in the automation’s behavior, then raise them to fit your workload.

​
When to use this template

  • Teams running on CircleCI who want the same auto-fix pattern as GitHub Actions users
  • Complex CircleCI workflows with multi-job orchestration
  • Reducing the friction of keeping legacy CI pipelines green
  • Auto-unblocking developers during major refactor work

​
Customization ideas

  • Scope to specific pipelines or branches
  • Tune the ACU cap based on typical pipeline complexity
  • Skip bot-authored commits to avoid fix-loops
  • Combine with SonarQube Quality Gate Fix for full quality automation

​
See also