Auto-update project docs from merged PRs via a scheduled Claude job

Configure a Claude Code scheduled cloud task that, once a day, clones the repo, lists PRs merged since the last run, reads the diffs, identifies affected .md files, edits them in place, and commits and pushes the doc updates back to the repo. Documentation becomes a continuously regenerated artifact rather than a thing humans curate.

Removes a recurring failure mode for any growing codebase. Once running, every merge is automatically reflected in the docs — onboarding pages, architecture notes, API references — without depending on engineer discipline.

1. Pick a docs structure: keep source-of-truth docs in /docs/*.md inside the same repo as the code.
2. Give Claude write access (commit/push) via a deploy key or a bot account scoped to that repo.
3. Set up a scheduled Claude task that runs daily. Have the agent list PRs merged in the last 24h via git log --since or the platform API.
4. For each PR, have the agent read the diff and propose doc edits limited to the touched modules or surfaces. Edit, commit on a branch named e.g. docs/auto-YYYY-MM-DD, open a PR.
5. Optionally auto-merge if a syntax-only or test passes; otherwise leave the PR for human review.
6. Watch the first week's output and tighten the prompt: which doc sections it's allowed to edit, what tone to keep, what NOT to invent.

• Hosting the job on the vendor cloud means your repo credentials live there. If that's a concern, point the schedule at a self-hosted runner (Mac mini or VPS) holding the credentials locally.