AI AGENTS
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionList open incident-driven runbook PRsGitHub
- ActionRead PR age, reviewers, and linked Sentry issueSentry
- LogicFilter to PRs idle past staleness threshold
- ActionAgent drafts context-rich nudge per PR
- OutputNudge reviewer in Slack; escalate stale PRs to leadSlack
What it does
Drafting the doc PR is only half the battle — they pile up unmerged. This agent runs daily, finds open GitHub PRs labeled as incident-driven runbook updates, and for each stale one writes a short reminder explaining the originating Sentry issue and why the doc matters, then nudges the reviewer in Slack. PRs idle past a threshold get escalated to the team lead.
When to use it
Use it when your team already opens doc PRs from incidents but they rot in review limbo, defeating the purpose. Keeps runbook fixes moving while context is fresh.
How it works
- 1A daily schedule starts the run.
- 2The agent lists open runbook doc PRs in GitHub and reads their age, reviewers, and linked Sentry issue.
- 3It filters to PRs idle beyond the staleness threshold.
- 4For each, it drafts a concise nudge with the incident context and what the doc closes.
- 5It pings the assigned reviewer in Slack; PRs stale past the escalation window are flagged to the team lead.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect SentryErrors, performance, releases.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More AI Agents workflows
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
Datadog Bill Spike Attribution Agent
When a daily Datadog cost check detects a spend jump, an agent attributes the increase to the specific services and metric types driving it and posts a ranked breakdown to Slack.
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.