Menu
Drive a pull request's CI checks to green — watch the check set, diagnose the root failure, apply the smallest fix, route it through review, then commit and push; repeat until green. Use when the user asks to "fix CI", "get the checks green", "loop on CI", or "the PR build is failing".
| name | fix-ci |
| description | Drive a pull request's CI checks to green — watch the check set, diagnose the root failure, apply the smallest fix, route it through review, then commit and push; repeat until green. Use when the user asks to "fix CI", "get the checks green", "loop on CI", or "the PR build is failing". |
| argument-hint | [<pr number or url>] |
Iterate on failing PR checks until they're green. Getting CI green inherently requires pushing, so this skill commits and pushes — but every fix goes through review first, and hooks are never bypassed.
Use gh pr checks for the check set — it covers all PR-attached checks, not just GitHub Actions (gh run list misses external checks). Re-read it after every push; the set can change.
gh pr view <number> --json number,url,headRefName
gh pr checks <number> --json name,bucket,state,workflow,link
$ARGUMENTS may name the PR; otherwise use the current branch.
Each round:
gh pr checks <number> --watch --fail-fast. If they've already failed, skip the wait and diagnose.gh run view <run-id> --log-failed
link to find the failing command or service.review-cycle is installed: run /review-cycle:review (it reviews, applies fixes, and marks the sentinel) — or /review-cycle:accept for a trivial one-line fix like a lint correction./review-cycle:review reviews and marks the diff but does not stage it, so git add the reviewed files yourself, then commit and push — never --no-verify.main: merge main in (then re-review and push) instead of bloating the PR with unrelated fixes.--no-verify) to force a check green.PR #<n> — CI: <green / still failing / stuck>
Rounds:
1. <check> failed — root cause: <…> — fix: <…> (reviewed via <review-cycle / approved>, pushed)
2. ...
Flakes: <none / <check> passed on retry>
Current checks: <summary>
Next: <PR URL once green, or what needs a human>
/review-cycle:review or get explicit approval.--no-verify).Mark the current uncommitted state as reviewed by updating the review sentinel. Use when you've manually reviewed the substance of your changes and want to commit without running the full /review-cycle:review cycle. Per-state escape hatch, lighter than the project-wide .claude/.no-review-gate opt-out marker.
Run the full automated code review cycle on uncommitted changes. First brings the tree to the project's canonical state (its own format/lint/typecheck). Fans out Codex and the auto-fix reviewers (code quality, tests, error handling, type design) in parallel, applies fixes inline per the embedded policies, and loops up to 4 iterations until clean. Then, once against the final state, runs the report-only reviewers (structural maintainability and spec conformance) and a de-slopify cleanup pass. Updates the review sentinel on completion. Does NOT commit.
Resolve merge or rebase conflicts with minimal, correctness-first edits, regenerate lockfiles with tooling, validate the build, and stage the result. Use when the user asks to "fix merge conflicts", "resolve conflicts", or after a merge/rebase leaves the tree conflicted.
Fetch and summarize review feedback on the active pull request into one prioritized action list. Use when the user asks to "get PR comments", "what did reviewers say", "summarize PR feedback", or "what do I still need to address on this PR".
Make a pull request easy to review without changing its behavior — a TL;DR that matches the diff, core files separated from generated ones, risks called out, and (only with approval) cleaner commit history. Use when the user asks to "make this easy to review", "tidy this PR", "clean up the commits", or "annotate the diff".
One-time setup for review-cycle. Verifies Codex CLI and multi_agent config, optionally appends comment + fix-vs-defer policies to CLAUDE.md (global or project), and updates .gitignore to exclude per-project sentinel files. Idempotent — safe to run multiple times.