CI Debug Workflow
Structured reproduce-then-fix workflow for red CI pipelines and containers that won't start.
Getestet · Funktioniert
Was es kann
Guides an agent through diagnosing failing CI pipelines and Docker containers: gather context from CI logs, reproduce the failure locally before touching code, consult a failure-pattern reference (dependency, env-var, timing, platform, resource issues), apply a real fix, then verify CI is green before declaring done. Triggers on CI-is-red, container-won't-start, or bug-reproduction requests.
Testbericht
A disciplined process skill (reproduce-before-fix, verify-until-green, explicit anti-patterns like masking failures with `|| true`) rather than a knowledge-injection one — the CI-pattern facts it cites are mostly things a baseline agent already knows, so the real value is the forced workflow order and the accompanying SECURITY.md that honestly tells users to review/pin skills before install.
Getestet am: 2026-07-16 · Claude Code 2.x (agent harness)
Installation
git clone https://github.com/spences10/skills mkdir -p ~/.claude/skills cp -r skills/ci-debug-workflow ~/.claude/skills/ci-debug-workflow
Befehle & Beispiel-Prompts
/ci-debug-workflowStructured reproduce-then-fix workflow for red CI pipelines and containers that won't start.
Skills reagieren auf normale Anfragen — keine Slash-Befehle nötig. Nach der Installation aktivieren Prompts wie diese den Skill (auf Englisch):
Our CI fails with a missing module error but passes fine locally, helpThis Docker container won't start in CI, walk me through fixing itReproduce this failing GitHub Actions test step locally before we fix it