Wait for CI so you don't have to
Poll gh pr checks every 10 minutes and get told when the PR is ready to merge, or a summary of which checks failed and why.
/loop 10m run `gh pr checks 1234`; if all pass, tell me it's ready to merge; if any fail, summarize which and why
claude-code · codex · cursor
Implementation note
Read-only and cheap. Replace 1234 with your PR number and go do something else.
Source: louiswharmby ↗graded C · 55/100 — how grades work →
More ci loops
Get the build green
Run the build, fix the first error, and repeat until npm run build exits 0, with a 10-turn cap.
/goal `npm run build` exits 0 — run the build, fix the first error, repeat until it succeeds; stop after 10 turns
cilow risk
Get the build green, every time
Work through each task in .toh/plan.md, fix blockers, until the build command succeeds or you hit 40 turns.
/goal every task in .toh/plan.md is checked and the build command exits 0 — or stop after 40 turns . A Haiku evaluator judges the condition FROM THE TRANSCRIPT — one more reason the QC gate quotes actual output: unquoted results are invisible to the evaluator. |
cimedium risk
Get lint and E2E tests passing
Execute work from PLAN.md until npm run lint and npm run test:e2e pass, scoping changes per AGENTS.md.
/goal Implement the work described in PLAN.md. Stop only when npm run lint and npm run test:e2e pass. Follow AGENTS.md, keep changes scoped, and report verification evidence Stop after 25 turns even if the goal is not reached.
cimedium risk