Keep docs in sync with main
On every push to main, check whether changed code drifted from the docs in /docs and open a PR fixing anything out of date.
/schedule on every push to main, check whether the changed code drifted from the docs in /docs, and open a PR fixing anything out of date
claude-code · codex
Implementation note
Because it opens PRs rather than pushing directly, a human always reviews the doc changes. Fires on every push, so cost scales with commit volume.
More docs loops
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
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
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