Read failing CI logs and suggest a fix
`additional_permissions` 'Currently supports actions: read' (usage.md).
workflow_run: completed (failure)
Est. cost per run~$0.35Checked Oct 16, 2026
Not executed· 1 caveatJust shippedOur pick for the best security, implementation, and planning skills.Best skills for each job.See the picks →
Workflows
GitHub Actions you can paste into a repo. Filter by the coding agent that runs and by what starts the run, then open a workflow for the YAML and the setup.
4 workflows
`additional_permissions` 'Currently supports actions: read' (usage.md).
workflow_run: completed (failure)
Est. cost per run~$0.35Checked Oct 16, 2026
Not executed· 1 caveatWhen CI fails on a pull request, Claude reads the failure logs, makes a fix, and pushes it to a new branch for you to review. The upstream file warns that it runs PR code with write permissions, so use it only on trusted branches.
workflow_run: CI completed (failure)
Est. cost per runUnknown (not estimated)Checked Oct 17, 2026
Not executed· 1 caveatWhen CI fails, Claude uses structured output to decide whether the failure looks flaky. Flaky runs are retried automatically; real failures are left for a human.
workflow_run: CI completed (failure)
Est. cost per runUnknown (not estimated)Checked Oct 17, 2026
Not executed· 1 caveatWhen CI fails on a pull request that has the auto-fix label, Claude pushes a fix commit to the branch. The number of auto-fix attempts per branch is capped.
workflow_run: CI completed (failure), opted-in PRs only
Est. cost per runUnknown (not estimated)Checked Oct 17, 2026
Not executed· 1 caveat