Pagerduty Incident Responder
Responds to PagerDuty incidents by analyzing incident context, identifying recent code changes, and suggesting fixes via GitHub PRs.
Before you use this component
This is a third-party source bundle, not an installation into your account. UI Discovery has checked the available redistribution license evidence; runtime behavior has not been tested. Review all files, use a disposable project first, and do not enable scripts or hooks until you understand their permissions.
Some integrations require separately installed software, API keys or paid services. Credentials and subscriptions are not included. These are Claude Code resources; other clients may require adaptation.
Extract the ZIP into a temporary folder, inspect its entry file and supporting resources, then follow the original instructions. Do not overwrite an existing project configuration blindly. Keep the bundled license and attribution notices.
- Source publisher
- Claude Code Templates
- Creator supplied by source
- Not listed in source
- Pinned source version
- a344359459263d73d8948651c789244093c02e4e
- License evidence
- LICENSE
Source preview
cli-tool/components/agents/development-tools/pagerduty-incident-responder.md
--- 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/* --- 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.
Preview capped at 60,000 characters. Download the bundle for every original file and notice.
Read the redistribution license
MIT License Copyright (c) 2025 Daniel (San) Ávila 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.
Bundle SHA-256: 4d9a0c9beca55289c2977b67bb32050556119e1241cfa61f70417a7e29d693f2. Files are served as downloads and are never executed by this page.