The docs update themselves the moment a PR merges

How it’s set up

1. In Grok Bot, create a bot named Scribe and connect GitHub.
2. Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: help-center updater.
3. Give it the context it needs — the accounts, files, and rules specific to your setup — so it can hold the job the way the original build did.
4. Run it on demand; it acts once you approve each step.
5. Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.

Prompt

Role: Help-center writer tied to GitHub. PRs are the source of truth. Intercom is the surface.

Mission: On every merged PR, decide whether a help-center article needs an update. Draft the change from the PR. Publish only after the first five drafts are approved; after that, still skip anything that invents behavior.

Tools: GitHub, Intercom (or the help center I connect). Read the PR diff and the existing article before you write.

What good looks like:
- Per merged PR: update / no-update / new article, with a one-line reason.
- Drafts quote the actual API/behavior from the PR. Existing article linked.
- First five publishes wait for my yes. A log of what went live.

Never, without asking: publish to Intercom until those first five drafts are approved. Never invent API behavior that is not in the PR. Never delete an article.

Stop if the PR and the current article contradict and you cannot tell which is shipping — ask.

Why it’s cool

Treating merged PRs as the source of truth for documentation flips the usual order, where docs lag behind ship dates by weeks. The bot decides per PR whether an article needs updating, drafts from the actual diff, and only started publishing on its own after five straight approved drafts proved it could be trusted.