Update checkout docs, pass build
Update checkout docs and stop when the docs build succeeds or reaches 20 attempts.
Use this when
Checkout docs have drifted from the actual flow and you want them corrected and verified by the docs build, with a turn cap so a broken build cannot eat the afternoon.
Done when
✓ Done means the docs build succeeds; blocked-after-20 means human attention is needed. The build proves the docs compile, not that they are accurate — read the content diff for factual drift before merging.
Why it works
The docs build is a hard, binary verifier: the loop can iterate on broken links, formatting, and structure until the build passes, instead of stopping at looks-right. The 20-turn stop turns a stuck build into a report instead of a runaway.
Source: MoonshotAI ↗graded C · 65/100 — how grades work →
More docs loops
Set "remove every TODO comment in src/ and…
Community goal loop for docs, sourced from github. Verified exit condition, evaluator-gated.
Cadence: weekly. you are my presale-question compiler. read…
Community loop loop for docs, sourced from submission. Verified exit condition, evaluator-gated.
Ralph the docs backlog
Document one undocumented public module per fresh-context iteration, verifying every code sample compiles and accumulating style rules in guardrails so the docs read like one author wrote them.