← ClaudeAtlas

afk-mergelisted

Lands an afk wave on dev — merges the green PRs in base order, checks off in docs/spec.md the criteria whose command really passes, takes the reds out, and says whether the loop continues or stops. Runs after each run, with nobody watching. Triggers: /afk-merge, "land the wave", "merge what is green", "do we continue?".
Warshoow/afk.sh · ★ 3 · AI & Automation · score 69
Install: claude install-skill Warshoow/afk.sh
# /afk-merge The run is over. This skill lands what holds, leaves the rest outside, and decides the loop's only question: **do we launch one more wave?** It does not diagnose the reds — `/afk-debrief` does that, better, and without redoing it here. This skill decides; the other one explains. ## The rule **A criterion is only checked off after its command has passed on `dev`.** Not because the ticket is green, not because the PR is merged, not because the work looks done. We run the command, we read the return code. That is what makes the counter mechanical. A model that checks off by reading ends up checking everything off. ## 1 — The state ```bash cat .afk/summary.md git fetch -q origin && git switch -q dev && git pull -q diff <(git show afk-spec:docs/spec.md | sed 's/\[x\]/[ ]/g') <(sed 's/\[x\]/[ ]/g' docs/spec.md) ``` The `diff` returns nothing other than boxes, otherwise **the loop stops**: the spec has drifted, nothing judges it any more. No `.afk/summary.md` → no run made it to the end. Merge nothing, say so. ## 2 — What is allowed to land A ticket lands if **all three** are true: | | where it is written | |---|---| | `GREEN` in the summary (not `OK` — `OK` contains the unproven greens) | `.afk/summary.md` | | the PR is not a draft | `sget <n> draft` | | the PR's CI is green | `gh pr checks <n>` | An `unproven green` (local gate shrunk **and** CI inconclusive) does not land: nobody ran the complete gate. It goes out as `ready-for-human`. ## 3 — Merging, i