CONTENT CREATION
Flag stale docs on every merged PR and draft the fix
When a PR merges, the agent compares the code diff against your docs and, if it finds documentation that the change made wrong, opens a draft PR with the corrected text…
How it runs
The automated pipeline, trigger to output.
- TriggerPull request mergedGitHub
- ActionFetch diff and changed filesGitHub
- ActionFind docs referencing changed codeGitHub
- LogicClassify each doc: stale, maybe, or unaffected
- ActionRewrite affected doc passages
- OutputOpen draft doc-fix pull requestGitHub
What it does
Watches your repository for merged pull requests, reads the actual code diff, and decides whether any documentation in the repo is now inaccurate because of it. When it finds a real mismatch, it drafts the corrected prose and opens a follow-up pull request so a maintainer only has to review and merge.
When to use it
Use it when your README, guides, or in-repo docs drift out of date because code changes ship faster than anyone updates the docs. Best for teams that keep documentation in the same repo as code and want doc fixes to arrive as reviewable PRs rather than nagging reminders.
How it works
- 1A merged pull request fires the trigger.
- 2The agent pulls the full diff and the list of changed files from GitHub.
- 3It locates docs that reference the changed code (function names, flags, endpoints, config keys).
- 4A decision step judges whether each doc is now wrong, vaguely affected, or untouched.
- 5For genuinely stale docs, it rewrites only the affected passages.
- 6It opens a draft pull request with the edits and a summary of what changed and why.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 3Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 4Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Content Creation workflows
On-demand: turn a blog URL into narrated B-roll clips
Accepts a blog URL via webhook, scrapes the article, generates a B-roll clip per paragraph with Replicate and a voiceover with ElevenLabs.
Sync a Figma master frame into localized hero renders
Pulls the current master hero frame and its text layers from Figma, generates a localized image variant for each locale defined in Airtable.
Build a Dropbox B-roll library from exported blog drafts
Triggers when a new blog draft file lands in a Dropbox folder, generates a Replicate B-roll clip for each paragraph.
Generate B-roll clips when a blog post is marked Ready in Notion
Watches a Notion blog database for posts flipped to 'Ready', splits the body into paragraphs, and generates a short B-roll video clip for each paragraph with Replicate.
Weekly: clip last week's top blog paragraph and post to socials
Runs on a weekly schedule, picks the highest-traffic paragraph from the past week's posts, generates one polished B-roll clip with Replicate.
On-Demand Screenshot Freshness Report from a Slack Command
A writer requests a freshness check in Slack for a specific docs page; the workflow inspects every screenshot on that page, scores each by age and version gap.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.