README freshness check
Once a week, verify every command, path, and badge in the README actually works against the current codebase and open a PR fixing anything stale.
/schedule every Friday at 3pm, verify the README: run each documented setup and usage command in a clean checkout, check that referenced files and scripts exist, and open a PR correcting anything that fails or has drifted, with a note explaining each fix
claude-code · codex
Implementation note
READMEs rot fastest right after big refactors, so this pays for itself in active repos. All changes arrive as a reviewable PR.
Source: looprepo ↗graded C · 55/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.
/goal set "remove every TODO comment in src/ and explain each removal" stop after 8 turns
docslow risk
Cadence: weekly. you are my presale-question compiler. read…
Community loop loop for docs, sourced from submission. Verified exit condition, evaluator-gated.
/loop cadence: weekly. you are my presale-question compiler. read presale-q-STATE.md: the question tally and the answer bank index. sweep the week's inbound [DM export / comments / presale emails] for questions from people who had not bought yet; tally them, the same question in different words counts as one. each round, take the single most-asked question without a bank entry and write a full FAQ answer plus a short paste-able DM snippet; answers get LINKED from then on, never retyped. if a new question contradicts an existing bank entry, flag it. append the tally and the new entry to presale-q-STATE.md; draft only, never publish the FAQ yourself. verification: a round is valid only when the new entry is appended and readable in presale-q-STATE.md. stop after 10 iterations, or until no question remains above [X] asks without an entry, whichever comes first; a contradiction escalates as BLOCK.
docslow risk
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.
/loop fresh context each iteration: read docs-backlog.json, docs/STYLE.md, and .ralph/guardrails.md; pick the top undocumented module, write its reference page with a runnable example, execute the example to prove it works, and mark the module done; add any style or structure decision to .ralph/guardrails.md; stop when the backlog is empty or after 20 turns
docsmedium risk