Opt-in workflow for fixing one GitHub issue end to end. Invoked only via `/fix <github-issue-url>` (`$fix` in Codex). Reproduces the bug with our own fixtures, implements the root-cause fix, gets clean independent reviews, opens a draft pull request, makes CI green, runs the Big Bonk review loop and marks the PR ready.
95%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Issue: $ARGUMENTS
Take ownership of the issue from investigation through a review-ready pull request. Do not stop at a diagnosis, a speculative patch or a locally passing test.
Establish the issue's live state below, then follow references/rules.md to confirm, reproduce, fix, validate and write the PR. Its "Automated Runs" section doesn't apply here. This file covers the review and CI loops that follow.
Require one GitHub issue URL, passed as the /fix argument. If it is missing, ask for it. If it names a repository other than the current checkout, find an existing checkout of that repository before editing.
git fetch origin main and branch from it. The local main ref is often stale: squash or diff against git merge-base HEAD origin/main, never local main.gh reads, keep first: small, and stop when fewer than ~1,500 calls remain.gh.gh pr list --search "<number>", git log origin/main --grep). Continue an existing PR instead of duplicating it. Before pushing to or stacking on a PR, check gh pr view <n> --json state: a squash-merged branch still looks unmerged to git.fix/<short-slug>), or use the fresh worktree branch created for this task.AGENTS.md, then work through references/rules.md up to its PR section.After the fix and focused validation pass, spawn one independent review sub-agent.
AGENTS.md, references/rules.md and the validation evidence. Don't tell it the intended answer or that the change is correct.NO FINDINGS verdict when clean.references/rules.md describes, and open a draft PR against main. For stacked PRs, use gh stack.gh pr checks <n> --watch. Don't end a turn with CI running and nothing watching it.gh run rerun <id> --failed, on the newest run for the head). For Next.js deploy-suite tests, decide flakiness from the last ~25 full runs' deploy-suite-report artifacts, never a dispatched rerun.gh pr view --json mergeable after each push. A conflicting PR gets no CI runs: rebase it.After each meaningful push, once local targeted tests and vp check pass, post a PR comment with exactly:
/bigbonk review for issues
Please review exact head `<sha>` without modifying or pushing the branch. Report all actionable findings within your 8-minute time limit.Take <sha> from git rev-parse HEAD right after pushing, not from gh pr view, which lags. Never tell Bonk what changed, what to focus on or which findings to confirm. For transform or analysis PRs prone to edge-case churn, you may add that it should only flag issues affecting real-world usage. Never use /bonk, only /bigbonk.
Before triggering, check gh run list --workflow bigbonk.yml for a run in progress for this PR (its title is the PR's title; runs for other PRs don't matter). If one is, wait for its review first.
Watch CI in parallel. If CI goes red, fix it before the next round.
Watch for the first new ask-bonk comment or new PR review posted after the trigger, and address it the moment it lands. Don't re-trigger a silent run before 10 minutes. If a run's log goes quiet for several minutes, cancel it and re-trigger. A posted verdict wins over a later "cancelled" notice.
Handle every finding as "Review Findings" below. Reply to each declined finding in the next trigger comment, then re-trigger on the new head right away. A decline doesn't end the loop.
Continue until the latest review on the latest head approves or reports no actionable findings. There is no round cap while findings stay in scope.
After a stack rebase, re-trigger only PRs whose own diff changed (compare git patch-id --stable). A rebased PR with an identical diff keeps its LGTM.
If Bonk pushes whitespace-only pnpm-lock.yaml commits, revert them. On a fork PR whose lockfile differs from main, merge main into the branch before re-triggering.
If a contributor pushes to the branch mid-review, don't adopt their change because it looks equivalent. Keep your own commits as the source of truth, audit theirs from scratch, and let the user decide.
Handle sub-agent, Bonk and clanky findings as "Review Findings" in references/rules.md says. Reply to findings on the PR, batched into the next trigger comment, and raise out-of-scope findings and scope creep with the user.
Mark the draft ready with gh pr ready <n> once all of these hold:
clanky reviews a PR only once it is ready. Read its full review and inline comments (gh api --paginate repos/{owner}/{repo}/pulls/<n>/reviews and gh api --paginate repos/{owner}/{repo}/pulls/<n>/comments), including INFO findings and "approved with comments", and handle them as "Review Findings". Once they are handled, comment clanky review to request a fresh review, and treat that as another round.
Report the issue, branch, PR URL, root cause, regression test, local validation, CI state, the review and Bonk verdicts, clanky's findings, and every declined finding with its reason.
If blocked by permissions, missing secrets, an outage or an unreproducible report, leave the PR in draft and state the exact blocker and the next action needed.
cloudflare/vinext
b0587b3
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.