nightly-docs-and-changelog

A configuration of [loop-controller]. That skill supplies the loop machinery — primitive selection, the full guardrail stack, state externalization. This skill supplies the three things specific to "keep an existing repo's docs+changelog from rotting on a nightly cadence": the per-night recipe (it diffs since the last run and authors the doc + changelog updates for that surface itself, following the documentation conventions [docs-agent] defines — docs-agent is the orchestrator's build-phase role and is not user-invocable on a schedule), the mechanical proof (docs match the changed surface AND every user-relevant change is recorded, ending in a reviewable PR), and the HITL boundary (it opens a PR and stops — it never merges docs). Read loop-controller for the guardrails; they're inherited, not repeated here.

Why disable-model-invocation: this loop edits docs, writes the changelog, commits, and opens a PR on its own, on a schedule. It is user-scheduled — you set it up once (or type /nightly-docs-and-changelog), not have Claude silently start rewriting docs because some code changed during the day.