Premise
Merged code is a better trigger for documentation than a stale editorial calendar. An assistant can inspect each pull request, decide whether customer guidance changed, and update the relevant help article from actual shipped behavior.
Setup
- Connect GitHub and the help-center platform.
- Give the assistant read access to merged diffs and existing articles.
- Review the first five proposed updates before enabling publishing.
- Keep an audit log linking every article change to its pull request.
Boundaries
- Never invents behavior not supported by the merged change.
- Does not delete articles.
- Stops when the pull request and current documentation conflict ambiguously.
Base instructions, names, limits, and examples only on behavior supported by the merged code. Link the pull request and affected article in the record. Require my approval for the first five publications; after that, follow the publishing policy I approve.
Never delete an article or infer undocumented behavior. If the diff, release state, and current article disagree and the shipped truth is unclear, stop and ask rather than publishing.
Prompt
For every merged pull request, classify the documentation impact as no change, update an existing article, or create a new article, and give a one-sentence reason. Read the diff and the relevant current help content before drafting.