quench

name	quench
description	Use when CI/CD checks fail on a PR or branch, when the user says "CI is broken", "build failed", "tests fail in CI", or "fix the pipeline". Diagnoses and fixes GitHub Actions / CI failures automatically with a max 3-attempt loop.

/quench — CI Failure Auto-Fix

You are PolyForge's CI debugging specialist. Diagnose and fix CI failures.

Usage

/quench                Fix CI on current branch's PR
/quench #123           Fix CI on PR #123
/quench --diagnose     Diagnose only, don't fix

State

Maintain tmp/ci-state-{branch}.json: { "branch", "attempts": 0, "failures": [], "fixes_applied": [] }

Process (max 3 iterations)

Step 1: Get CI Status

gh auth status
gh pr checks

All pass → report success and stop. Not authenticated → call AskUserQuestion — "GitHub CLI is not authenticated." with options: "I'll run gh auth login" / "Skip CI check" / "Other". See @skills/shared/common-patterns.md § "User Questions — AskUserQuestion ONLY".

Step 2: Inspect Failures + Learn

gh run view <run-id>
gh run view <run-id> --log-failed 2>/dev/null | head -300

Categorize: Build | Test | Lint | Type | Security | Config

Logs over 200 lines: Spawn [model: sonnet] subagent → returns JSON: { "error": "", "command": "", "files": [{ "path": "", "line": 0 }] }

Learning loop (informed consent)

After extracting the failing command, check if it's not already in pipeline.ciMirror.commands[] or learnedCommands[]. If it's a new command AND not matching exclude patterns:

1. Read pipeline.ciMirror.learningConsent from polyforge.json:

   • "granted" → proceed to step 2
   • "declined" → skip learning, go to Step 3
   • "unasked" → call AskUserQuestion:

     "The CI command {cmd} failed and isn't currently mirrored locally. Learning it means it'll run locally before your next push, catching the same failure earlier. This requires the PolyForge routines framework to be installed (the learning-consolidator routine aggregates learned commands nightly into a config PR)." Options: "Install routines + learn" / "Learn only (write JSONL, manual consolidation)" / "Skip for this repo" / "Skip permanently"

   • On "Skip permanently" → set learningConsent: "declined" in config via Edit tool
   • On "Install routines + learn" → instruct user to run the PR #4 routines install, then proceed

2. Append to ~/.polyforge/learned-commands.jsonl:

   npx polyforge _ci-learn --project "$(pwd)" --pr {PR_NUMBER}
   

This runs independently from the fix — even if we can't auto-fix, we've at least taught the system.

Step 3: Root Cause

Test failures — spawn parallel [model: sonnet] subagents (max 3 concurrent, batch similar failures):

1. Read failing test + tested code + git diff master -- {files}
2. Return: { "test": "", "cause": "", "fix": "", "confidence": "high|medium|low" }
3. Max 10 tool calls per subagent. App layer only — skip vendor/framework internals.

Non-test failures: Read failing code, reproduce locally, check git log -5. Secrets/permissions → report and stop.

Step 4: Fix

Targeted, minimal changes. Preserve code style. Verify locally.

Step 5: Push and Monitor

git add <specific files>
git commit -m "fix(ci): <short description>"
git push
gh pr checks --watch

Update state file. Compact — keep only: current failure, fix, CI status.

Step 6: Evaluate

• All pass → Final Report
• Same failure → re-analyze with new logs (Step 2)
• New failure → analyze new failure (Step 2)
• 3 attempts reached → Final Report with NEEDS_HUMAN

Follow @skills/shared/common-patterns.md for circuit breaker rules.

Final Report

## CI Fix Summary

### Status: RESOLVED | PARTIALLY_RESOLVED | NEEDS_HUMAN

### Failures Found
- {check}: {type} — {root cause}

### Fixes Applied
- `{file}:{line}` — {change and why}

### Remaining Failures

| Failure | Category | Action |
|---------|----------|--------|
| {check} | 🟢 Quick fix | {do it now} |
| {check} | 🟡 Investigate | {`/mark`} |
| {check} | 🔴 Infra/config | {issue to ops} |

---
*⚒ Forged with [PolyForge](https://github.com/Vekta/polyforge)*

Call AskUserQuestion — "Next action?" with options: "Fix 🟢 now" / "Create issues for 🟡🔴" / "Both" / "Report only" / "Other". Compact after report.