skills.rest
cnoe-io
cnoe-ioOFFICIAL
Explore all skills by this author →
WebsiteGitHub

oncall-handoff

Aggregate PagerDuty incidents, Jira issues, and ArgoCD deployments into a structured handoff document.

392|73|Updated Jun 12, 2025
Search Tags:#handoff#argocd#jira#on-call#deployments#pagerduty
One-click install
npx skills add https://github.com/cnoe-io/ai-platform-engineering --skill oncall-handoff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: oncall-handoff
Source: https://github.com/cnoe-io/ai-platform-engineering/tree/main/ui/src/skills/oncall-handoff
Command: npx skills add https://github.com/cnoe-io/ai-platform-engineering --skill oncall-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

On-call handoffs are error-prone and time-consuming. This Skill aggregates open incidents from PagerDuty, ongoing Jira issues, and recent ArgoCD deployments to produce a clear, ready-to-use handoff document for the incoming engineer.

Core Features & Use Cases

  • Automated data aggregation: collects active incidents, on-call schedules, open Jira issues, and deployment statuses into a single, structured document.
  • Cross-tool orchestration: coordinates PagerDuty, Jira, and ArgoCD data to ensure stakeholders understand current state and next steps.
  • Actionable handoffs: outputs a concise document with clear owner, priorities, and upcoming changes for shift transitions.

Quick Start

Instruct the AI to generate the latest on-call handoff document for the current shift.

Frequently Asked Questions about oncall-handoff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an on-call handoff document for shift transitions?▼

To generate an on-call handoff document, aggregate active PagerDuty incidents, open Jira issues, and recent ArgoCD deployments into a structured, action-oriented summary. This provides the incoming engineer with current system states, priorities, and upcoming maintenance steps.

What is the best way to automate incident aggregation for on-call rotations?▼

Automating incident aggregation for on-call rotations involves cross-tool orchestration across PagerDuty, Jira, and ArgoCD. It collects active incidents, deployment statuses, and on-call schedules into a single ready-to-use handoff document.

Does this on-call handoff approach work with ArgoCD deployments and Jira issues?▼

Yes, on-call handoff generation works with ArgoCD and Jira by coordinating data from both platforms. It retrieves recent ArgoCD deployment statuses and open Jira issues to ensure stakeholders understand current infrastructure changes and pending tasks.

Can I use PagerDuty schedules to create an action-oriented handoff summary?▼

Yes, you can use PagerDuty schedules to create an action-oriented handoff summary. The process extracts active PagerDuty incidents and on-call schedules, combining them with Jira and ArgoCD data to define clear owners and priorities for the incoming shift.

What is included in a cross-tool on-call handoff document?▼

A cross-tool on-call handoff document includes active production incidents, open Jira issues, recent ArgoCD deployments, and the current on-call schedule. This structured output delivers a concise overview of system state and required next actions.

Related Skills

Explore More Software Engineering Skills→
cnoe-iocnoe-io
392

incident-investigation

Correlate PagerDuty incidents with Jira tickets and ArgoCD deployments into a timeline.

Official
Intermediate
JhabbigJhabbig

on-call-handoff-patterns

Creates a searchable archive of product pages and their metadata.

Community
Advanced
zangxin75zangxin75

gitflow

Automate code pushes and monitor CI/CD pipeline status across GitHub and GitLab.

Community
Intermediate
DojoGenesisDojoGenesis
2

agent-performance-report

Generate aggregated performance reports from stored trace data.

Community
Advanced