Keep documentation up-to-date
Draw on code and other sources to keep documentation up to date automatically.
Have ZeroTwo set source code changes against the public docs, the release notes, and PR context, then write targeted documentation updates, with steps for checking them, before anything goes live.
Related links
Best for
- Developer docs, READMEs, runbooks, and migration notes tracking fast-changing behavior.
Skills & Plugins
- GitHubReads issues, pull requests, and review threads, and its
gh-fix-ciskill inspects failed checks.
Starter prompt
Introduction
Update docs with the code: ZeroTwo reads diffs, tests, and PRs, then drafts a scoped edit.
How to use
- Share the branch, PR, or files, and say what must stay private.
- Have ZeroTwo search the docs for the feature names, config keys, and commands the change touches.
- Edit only what needs to change, keeping structure, terminology, and frontmatter.
- Run the docs checks and cite evidence for each claim.
What to give ZeroTwo
| Source | Value |
|---|---|
| Code and tests | Actual behavior |
| Public release notes | Public terminology and status |
| PR or issue | Why it changed |
| Docs checks | Definition of done |
Make the workflow repeatable
Record rules in AGENTS.md, package a skill, or schedule a task. Scheduled runs never stop for approval, so keep a scheduled docs task to drafting edits you review afterward.
- Check docs when user-facing behavior changes. - Only public information in public docs.
Related use cases
Create a CLI ZeroTwo can use
Hand ZeroTwo a composable command wrapping an API, a log source, an export or a team script.
Create browser-based games
Write a game plan and have ZeroTwo build it and try it out in a live browser.
Follow a goal
Hand ZeroTwo one lasting objective for long-running work.


