Hand off the pager without making the next engineer reconstruct the shift
On-call handoffs usually happen fast, right when context is easiest to lose. The next engineer starts their shift digging through incidents, deploys, noisy alerts, and half-finished Slack threads just to understand the current state. This recipe pulls the shift's PagerDuty incidents, deploy activity, Datadog alerts, and open Slack threads into a clean handoff brief the next on-call can use immediately.
Generate an on-call shift handoff brief for a DevOps or SRE engineer. Goal: Help me close out my on-call shift with a clear operational handoff so the next engineer does not have to reconstruct state from Slack scrollback. Ask me for: - Shift start and end (UTC) - Services I covered - Active investigations with current state - Anything I expect to recur on the next shift - Follow-ups I owe but did not finish - Any deploys or changes the next person should know about - Slack channel for the handoff post Use available integrations this way: - PagerDuty: list incidents during my shift, severity, and resolution status - Datadog: list alerts that fired during my shift, including ones that auto-resolved - GitHub: list deploys and merged PRs in services I covered during the shift - Slack: scan incident channels I was in for unresolved threads and decisions - Linear: list any tickets I created or updated during the shift - Google Docs: write the handoff brief - Google Calendar: create a 15-minute handoff sync if the next on-call wants one Output: 1. A handoff brief with shift summary, incidents, deploys, and alerts 2. Open investigations with current state and what is blocked 3. Pending action items with owners 4. Watch list of services to monitor 5. A short Slack post for the on-call channel tagging my replacement 6. A handoff doc in Google Docs linking to all the source incidents and PRs Rules: - Only include facts pulled from the integrations or that I provide - Do not infer root causes; describe symptoms and current state - Do not include private information from Slack DMs, only public channels - Treat all timestamps as UTC unless I specify otherwise - Flag any investigation older than 48 hours as stale
This recipe turns the end of an on-call shift into a structured
handoff. It pulls incidents from PagerDuty, deploys from GitHub,
alerts from Datadog, and unresolved context from Slack so the next
person starts with operational state, not guesswork.
Find stale runbooks before they fail during an incident
Runbooks go stale quietly. Deploy paths change, services move, dependencies get renamed, and the doc only gets noticed at 3 a.m. when it points to infrastructure that no longer exists. This recipe finds runbooks that have not kept up with the services they describe and proposes updates based on recent service changes.
Turn rough incident notes into a blameless postmortem with shippable follow-ups
Postmortems often start as rushed incident notes and stay messy until review time. This recipe takes a rough draft, removes blameful language, fills timeline gaps from PagerDuty and Slack, turns vague follow-ups into concrete Linear tickets, and schedules the review.
Fix credit report errors without guesswork
Generate dispute letters, evidence checklists, and follow-up timelines to correct credit report mistakes. Covers bureaus, furnishers, and identity theft.
Stop tax season from becoming a fire drill
A tailored documents list, question set, and recordkeeping system so you file accurately, claim what you're owed, and never scramble at the deadline again.