Support
Documentation freshness audit
Checks your written docs against the actual codebase every month and comments on the pages that have gone stale.
The prompt
This is the whole configuration
Paste it into a workflow and edit it in plain English. There is nothing else to wire up.
On the first of every month, audit our Engineering Docs in Notion against the codebase. For each page, find the files, environment variables, commands, and API routes it references, then read those files on the main branch of our GitHub repository. Flag a page as stale when it names something that no longer exists, describes behavior the code contradicts, or documents a default value that has changed. Leave a comment on each stale page saying exactly which line is wrong and what the code says now. Do not edit the pages themselves. Post a summary to #engineering listing the stale pages, ordered by how many people viewed them, and note any page you could not verify.
Trigger
What starts this agent
Example output
What you get back
Every run leaves a readable record: the steps the agent took and the result it produced.
6 stale pages flagged
- `Auth Setup` references a removed env var
- `Deploy Runbook` names an old cluster
- Each page commented with the specific line
New to Helios? Start with Run your first agent.
Related templates
Pair it with these
Engineering
Release notes writer
Turns a new tag into release notes grouped by theme, publishes them on GitHub, and files a changelog entry in Notion.
Marketing
Discord community digest
Reads every channel each evening, surfaces unanswered questions, and files real bug reports as GitHub issues.
Support
Slack support triage
Watches your support channel, answers what your docs already cover, and escalates the rest with the account context attached.
Run Documentation freshness audit on your stack.
Connect the integrations, paste the prompt, attach the trigger. The agent takes it from there.