| name | get-ci-green |
|---|---|
| description | Use when CI fails on a branch and you need a tight loop: reproduce locally, interpret logs, apply minimal fix, re-run. Triggers on "fix CI", "failing check", "GitHub Actions red", "pipeline broken". |
- Identify — Exact job name, step, and first error line (not only the summary).
- Reproduce locally — Same command CI runs (
npm test,ruff check, etc.). - Minimize — Smallest change that fixes root cause; avoid opportunistic refactors.
- Verify — Local command green; push; watch CI.
- Document — If flaky, add issue link or quarantine with owner and deadline.
- Lockfile drift — Regenerate lockfile with correct package manager version.
- Type/lint — Fix or narrow rule; do not blanket-disable without comment and issue.
- Tests — Order, time, network: make deterministic (clock, network mocks, seeds).
- Env — Missing secrets in CI: use repo settings; never commit secrets.
- Upstream outage: pin dependency or retry with backoff; track externally.
- If fix requires product decision, stop and surface options instead of guessing.