← Explore all agents

OPERATIONS AND RELIABILITY / GitHub partners

PagerDuty Incident Responder

Pulls a PagerDuty incident, correlates it with commits from the 24 hours before it started, and proposes a fix or rollback pull request.

“Responds to PagerDuty incidents by analyzing incident context, identifying recent code changes, and suggesting fixes via GitHub PRs.”

01 / THE REASONING

Why this made the selection.

  • It forms a triage hypothesis by root-cause category (code change, configuration, dependency, infrastructure) and compares the incident start with deployment times before searching code.
  • It must state its confidence level when the root cause is uncertain, and its response carries the incident URL, severity and commit SHAs.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • agents/pagerduty-incident-responder.agent.md
  • plugins/partners/plugin.json and README.md
  • LICENSE

Our findings

  • Listed in plugins/partners/plugin.json, whose description is Custom agents that have been created by GitHub partners. The commit history was not used to attribute authorship.
  • Fix pull requests are titled [Incident #ID] Fix for [description] and link the PagerDuty incident.
  • With several active incidents it prioritises by urgency and service criticality.

Not established by this review

  • The agent was not run.
  • No PagerDuty account was connected and no pull request was opened.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Use the role in your project.

Upstream setup instructions ↗

DOCUMENTED COMMAND

copilot plugin install partners@awesome-copilot

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

  1. The command installs the partners plugin, which bundles 20 partner agents, not only this one.
  2. For this agent alone, download the unchanged pagerduty-incident-responder.agent.md with its LICENSE.txt and place a reviewed copy in the workspace .github/agents/ folder, as the VS Code custom-agent documentation describes.
  3. Remove the GitHub write tools from your copy unless the agent should open pull requests and issues.
  4. Authorise the PagerDuty MCP server through OAuth when prompted.

Before you start

  • GitHub Copilot with custom agents
  • A PagerDuty account
  • The repository of the affected service

THE COMPLETE REVIEWED DEFINITION

Read it before you reuse it.

Original source bytes, with attribution.
Review the host-specific setup notes above.

---
name: PagerDuty Incident Responder
description: Responds to PagerDuty incidents by analyzing incident context, identifying recent code changes, and suggesting fixes via GitHub PRs.
tools: ["read", "search", "edit", "github/search_code", "github/search_commits", "github/get_commit", "github/list_commits", "github/list_pull_requests", "github/get_pull_request", "github/get_file_contents", "github/create_pull_request", "github/create_issue", "github/list_repository_contributors", "github/create_or_update_file", "github/get_repository", "github/list_branches", "github/create_branch", "pagerduty/*"]
mcp-servers:
  pagerduty:
    type: "http"
    url: "https://mcp.pagerduty.com/mcp"
    tools: ["*"]
    auth:
      type: "oauth"
---

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.

The download contains pagerduty-incident-responder.agent.md. Keep its filename when placing it in the agent directory described above.

By GitHub partners. Exact upstream source ↗ · Licence · Attribution

SHA-256 ab286be4abb1d5858b55966edc7973f4d1094b7da704f22f65886bfafc241971

Read the applicable licence
MIT License

Copyright GitHub, Inc.

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. Agent definition ↗Checked

    https://github.com/github/awesome-copilot/blob/156736fb63e965b2f547a1460f3b5972c46e6b24/agents/pagerduty-incident-responder.agent.md

    Supports: summary, upstreamDescription, whySelected, limitations, access, review

  2. https://github.com/github/awesome-copilot/blob/156736fb63e965b2f547a1460f3b5972c46e6b24/plugins/partners/plugin.json

    Supports: publisher

  3. https://github.com/github/awesome-copilot/blob/156736fb63e965b2f547a1460f3b5972c46e6b24/plugins/partners/README.md

    Supports: install

  4. https://github.com/github/awesome-copilot/blob/156736fb63e965b2f547a1460f3b5972c46e6b24/LICENSE

    Supports: license

  5. https://code.visualstudio.com/docs/copilot/customization/custom-agents

    Supports: install, compatibility

Evidence & Ask