How to do it
- Docs merge triggers a draft A GitHub Actions step sends a signed webhook when docs pages are added or significantly changed.
- Draft from the page itself The agent in Claude Code or VS Code reads the new page and drafts a post around the task it helps the reader complete.
- Accuracy review A technical writer approves, corrects terminology inline, or rejects drafts for internal-only pages.
- Screenshots with alt text Guardrails require alt text on screenshots and diagrams, which matches good docs practice anyway.
New tutorial: paginate through large API results without missing records when data changes mid-request. Covers cursor-based pagination, retries, and a complete Python example. About 15 minutes end to end.
Docs deserve distribution too
Technical writers care about accuracy above all, which is exactly why docs promotion has been hard to delegate. A generic marketing post about a docs page tends to overstate or blur the details. An agent that reads the actual page, working inside the same repo, produces a far more precise first draft. The writer's approval makes it trustworthy.
Setup
- Connect networks where your readers are. Developer audiences are on X, Bluesky, Mastodon, and LinkedIn.
- Add the MCP server to Claude Code or VS Code, so drafting happens where docs are written.
- Add a workflow step with GitHub Actions that sends a webhook on docs changes.
- Put product terminology and style guide rules in brand memory.
Permissions
The docs agent gets draft only. Technical writers approve. If your docs are versioned, add a rule in brand memory that posts must name the version. The audit log records which commit or page triggered each post, useful when docs are later revised.
Measuring docs promotion
Tag links with the UTM builder and watch docs analytics for visits, time on page, and completion of tutorials. Per-post metrics show reach where networks provide it. Over time you will see which kinds of pages, such as tutorials, references, or migration guides, draw readers from social.
Pitfalls
- Promoting every typo fix. Send only new pages or significant rewrites.
- Code in images. Prefer a short text snippet and a link; if you use an image, alt text must describe the code.
- Jargon without a task. Lead with what the reader can do after reading.
- Version drift. If a page is later updated for a new version, the old post may still circulate; link to the latest version URL where possible.
Templates: how-to thread, tips thread.