Set up automated CI fixing with Claude Code. Use when adding a workflow that analyzes failures, applies fixes, and files issues; pass --reusable for a multi-repo workflow_call template.
Set up automated CI fixing with Claude Code. Use when adding a workflow that analyzes failures, applies fixes, and files issues; pass --reusable for a multi-repo workflow_call template.
Current workflows: !find . -path '*/.github/workflows/*' -maxdepth 3 -name '*.yml' -type f
Claude secrets configured: !gh secret list
Parameters
Parse from $ARGUMENTS:
--setup: Create or update the single-repo inline workflow in .github/workflows/github-workflow-auto-fix.yml
--reusable: Create or update the reusable definition in (see Step 5)
workflow_call
.github/workflows/reusable-ci-autofix.yml
--caller: Create the thin caller workflow in .github/workflows/auto-fix.yml that invokes the reusable definition (see Step 5)
--workflows <names>: Comma-separated workflow names to monitor (default: auto-detect CI workflows)
--dry-run: Show what would be created without writing files
Default (no --reusable/--caller) generates the single-repo inline workflow described in Steps 1–4. --reusable/--caller switch to the reusable variant in Step 5.
Execution
Execute this workflow setup process:
Step 1: Assess current state
Check if .github/workflows/github-workflow-auto-fix.yml already exists
List all current workflow files and their name: fields
Check if CLAUDE_CODE_OAUTH_TOKEN secret is configured
Step 2: Select workflows to monitor
If --workflows provided, use those. Otherwise, auto-detect suitable workflows:
If --setup or workflow is missing, create .github/workflows/github-workflow-auto-fix.yml.
The workflow's display name follows <Domain>: <Action> (Auto-fix: is the canonical domain for workflow_run-triggered remediation; quote the value because YAML treats : as a key separator). The strings under workflows: must match the display names of the target workflows exactly — update both sides whenever a target's name: changes. See .claude/rules/workflow-naming.md.
When --reusable or --caller is passed, generate the workflow_call shape instead of the single-repo inline workflow. The full templates live in REFERENCE.md.
--reusable — create .github/workflows/reusable-ci-autofix.yml from REFERENCE.md § Reusable Workflow. Customize:
auto_fixable_criteria / not_auto_fixable_criteria defaults to match the project's tech stack
verification_commands default to match the project's linter/formatter commands
max_turns (default: 50)
--caller — create .github/workflows/auto-fix.yml from REFERENCE.md § Caller Workflow. Customize:
The monitored workflow name: strings in the workflows: list (display names — must match each target's name: exactly)
auto_fixable_criteria / verification_commands overrides for the project's tools
Display-name convention — the caller's name: follows <Domain>: <Action> (Auto-fix: CI failures is canonical; the reusable definition itself uses Reusable: CI auto-fix). Quote values containing colons. See .claude/rules/workflow-naming.md.
Validate both YAML files, list the monitored workflows, and confirm CLAUDE_CODE_OAUTH_TOKEN or ANTHROPIC_API_KEY exists.
The reusable variant adds dedup (max 2 open auto-fix PRs), workflow_dispatch with a pr_number input, and fan-out — see the Architecture and Safety Guards below, and REFERENCE.md for the rationale.
Architecture
Single-repo inline (default):
workflow_run (failure)
|
v
Gather logs & context
|
v
Claude analyzes failure
|
+---+---+
| |
v v
Fixable Complex/External
| |
v v
Fix & Open issue
push with analysis
| |
v v
Comment Comment on PR
on PR linking issue
The reusable variant wraps the same analyze→fix/issue core in a workflow_call definition fronted by a thin caller (workflow_run + workflow_dispatch with fan-out and a dedup gate). See REFERENCE.md § Reusable Workflow and § Cross-Repository Usage for the full templates.
