AutoGineer
Generated banner for Pagerduty Incident Responder
Generated logo for Pagerduty Incident Responder

Pagerduty Incident Responder

GitHubOfficialFirst committed by aaronpowellDistributed by GitHub

  • Custom agent
  • Workflow
  • Cloud and DevOps
  • MIT
  • No issues found
Download ZIP

From the author

Responds to PagerDuty incidents by analyzing incident context, identifying recent code changes, and suggesting fixes via GitHub PRs.
— the description by aaronpowell

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The PagerDuty Incident Responder is a specialized agent workflow designed to streamline the triage and resolution of service incidents. By integrating directly with PagerDuty and GitHub, the agent automatically retrieves incident context, identifies the responsible on-call team, and performs a forensic analysis of recent code changes. It correlates incident timestamps with commit history and deployment logs to formulate a root cause hypothesis, ultimately assisting engineers by drafting remediation pull requests.

What it does

  • Fetches detailed incident data from PagerDuty including service context and timeline.
  • Identifies the on-call team and relevant personnel for the affected service.
  • Analyzes incident data to categorize potential root causes like code changes or configuration issues.
  • Searches GitHub for recent commits and PRs within the incident timeframe.
  • Drafts remediation pull requests with appropriate titles and links to the original incident.

When to use it

  • When an active PagerDuty incident requires rapid investigation and correlation with recent code changes.
  • When you need to quickly identify which recent deployments or commits might have triggered a service degradation.
  • When you want to automate the initial triage steps and drafting of fix PRs for known service issues.

Advantages

  • Reduces mean time to resolution by automating the correlation between alerts and code history.
  • Provides a structured approach to incident triage and hypothesis generation.
  • Ensures consistent documentation by linking remediation PRs directly to PagerDuty incidents.
  • Helps identify the correct on-call stakeholders for faster escalation.

Usage examples

“Investigate PagerDuty incident ID 12345 and suggest a fix.”
The agent retrieves the incident details, identifies the affected service, searches for recent commits, and proposes a pull request to resolve the identified issue.
“Analyze recent incidents for the 'auth-service' and check for recent code changes.”
The agent lists active incidents for the service, correlates them with recent GitHub activity, and provides a summary of potential root causes.

Install

  1. Download the custom agent as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/github/pagerduty-incident-responder/download

  2. Extract the agent file into .github/agents, then commit it:

    mkdir -p .github/agents && unzip -j pagerduty-incident-responder.zip 'pagerduty-incident-responder/pagerduty-incident-responder.agent.md' -d .github/agents

  3. Keep the LICENSE and ATTRIBUTION.md files from the ZIP with your copy.

Documentation by aaronpowell

You are a PagerDuty incident response specialist. When given an incident ID or service name:

  1. Retrieve incident details including affected service, timeline, and description using pagerduty mcp tools for all incidents on the given service name or for the specific incident id provided in the github issue

  2. Identify the on-call team and team members responsible for the service

  3. Analyze the incident data and formulate a triage hypothesis: identify likely root cause categories (code change, configuration, dependency, infrastructure), estimate blast radius, and determine which code areas or systems to investigate first

  4. Search GitHub for recent commits, PRs, or deployments to the affected service within the incident timeframe based on your hypothesis

  5. Analyze the code changes that likely caused the incident

  6. Suggest a remediation PR with a fix or rollback

When analyzing incidents:

  • Search for code changes from 24 hours before incident start time

  • Compare incident timestamp with deployment times to identify correlation

  • Focus on files mentioned in error messages and recent dependency updates

  • Include incident URL, severity, commit SHAs, and tag on-call users in your response

  • Title fix PRs as "[Incident #ID] Fix for [description]" and link to the PagerDuty incident

If multiple incidents are active, prioritize by urgency level and service criticality. State your confidence level clearly if the root cause is uncertain.

Files

ATTRIBUTION.md

Attribution

This folder is an unmodified copy of the Agent Skill "pagerduty-incident-responder", distributed by AutoGineer (https://autogineer.com/agent-skills).

The skill's own files are unmodified copies. AutoGineer is not affiliated with or endorsed by the author or the publisher.

Files added by AutoGineer

  • ATTRIBUTION.md: this file, written by AutoGineer

  • LICENSE: copied from LICENSE

Requirements and compatibility

Written for: GitHub Copilot

Works with: GitHub Copilot

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

First committed by
GitHub avatar of aaronpowellaaronpowell
Publisher
GitHub (Official)
Distributed by
GitHub
Source
github/awesome-copilot · agents/pagerduty-incident-responder.agent.md · commit 797337f
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced
Contributors
aaronpowell

AutoGineer is not affiliated with or endorsed by aaronpowell or GitHub.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download pagerduty-incident-responder.zip