on-call-handover-writer
SkillMonitoring & opsFormats structured end-of-shift summaries covering active incidents, degraded services, and pending follow-ups.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the on-call-handover-writer skill
What this skill tells your AI
The instructions your AI receives, as published by codebygarv/ai-skills in skills/productivity/on-call-handover-writer/SKILL.md and read by ahel’s review.
Purpose
Generate concise, comprehensive, and actionable on-call shift handover reports to transfer operational context smoothly to the incoming engineer without lost details.
When to Use
- Weekly or daily on-call shift transitions.
- Handing over active or mitigated incidents across time zones (Follow-the-Sun).
- Summarizing alert volume and noise for engineering managers.
What to Analyze
- Active / Ongoing Incidents: Any un-resolved or partially mitigated P1/P2 issues.
- Recent Deployments & Feature Flags: High-risk changes toggled during the shift.
- Flaky Alerts & False Positives: Alerts that paged repeatedly without actionable issues (alert fatigue).
- Follow-Up Action Items: Jira postmortem tickets or bug fixes assigned during the week.
- Upcoming High-Risk Events: Scheduled database maintenance, marketing campaigns, or cutovers.
Output Format
- Shift Overview: Dates, Outgoing Engineer, Incoming Engineer, Total Pages (P1/P2/P3).
- Incident Summary Table: [Incident # | Severity | Status | Current Mitigation | Next Action].
- Alert Noise & Tuning Candidates: Specific alerts that need threshold relaxation.
- Scheduled Maintenance & High-Risk Items: What the incoming on-call must watch for.
Avoid
- Writing a 10-page unorganized wall of text.
- Leaving active workarounds undocumented.
Signals
- GitHub stars
- 25
- Forks
- 1
- Last commit
- Aug 2026
Advanced
- Catalog kind
- skill
- Gateway key
on-call-handover-writer- Source
- github.com/codebygarv/ai-skills