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.
claude-code
More docs loops
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
docshigh risk
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
docsmedium risk
Changelog generation from commits
Turn the commit history since the last release tag into a human-readable, categorized CHANGELOG entry ready for the next version.
/goal CHANGELOG.md has a complete entry for the next release — read every commit since the last version tag, group changes into Added, Changed, Fixed, and Removed, write user-facing descriptions (not commit messages), link PR numbers, and flag anything that looks like a breaking change; stop after 5 turns
docslow risk