Monitors merged PRs and automatically creates follow-up PRs with documentation updates when code changes affect existing docs.
- Identifier
auto-docs-update- Version
- 1.0.0
- Steps
- 3
- Triggers
- 1
- documentation
- automated
- merge
- docs-update
When it runs
pull_request.merged- Settle delay
- 60s after the event
Only when all hold
- pullRequest.baseBranch in main, master
- actor.username not in dependabot, renovate, github-actions
- actor.username not contains [bot]
The pipeline
The graph below is the one the workflow opens with in the builder — same steps, same layout, drawn on the same canvas. The run playing through it is a simulation; the branches and conditions are real.
- 01PR Merged
triggerThe event that starts the run.
- 02Clone Repository (main)
git.cloneShallow-clones the repository at the right ref.
- 03Update Documentation
agent.runOne agent works the task with its toolkit.
The agent
Docs Update Writer
- Base type
- Tech Writer
- Temperature
- 0.3
- Max iterations
- 30
- Tools
- 9
Git provider · 4
get_pull_request_diffGet Pull Request Diff · readcreate_branchCreate Branch · writecreate_pull_requestCreate Pull Request · writecreate_issue_commentCreate Issue Comment · write
Filesystem · 4
read_fileRead File · readlist_dirList Directory · readwrite_fileWrite File · writeedit_fileEdit File · write
Code search · 1
code_searchCode Search · read
Related playbooks
Changelog Generator
Classifies each merge to the default branch and adds a changelog entry.
Release Notes
Generates clean, categorized release notes from merged PRs when a release publishes.
Auto Update AGENTS.md
Nightly scan that keeps the AGENTS.md AI-context file current, opening a PR only when it drifts.