PagerDuty

PagerDuty's own plugin for Claude Code. Its risk-scoring command reads your uncommitted git changes, pulls the incident history of the PagerDuty service behind the repository, and looks for overlap between what you're changing and what has caused incidents before. You get a risk score and recommendations before you commit. What you can do with it - Run /pagerduty:pre-commit-risk-scoring to assess your uncommitted changes - See active incidents on the service and a summary of its last 90 days of incidents - Get a risk score from 0 (no risk) to 5 (critical), with the risk factors behind it and a recommendation - Spot correlations between the files you're changing and past incidents and change events - Create or update PagerDuty skills for the SRE Agent through a guided interview with /pagerduty:create-pagerduty-skill (Early Access) How it connects In Claude Code, run /plugin marketplace add pagerduty/claude-code-plugins, then /plugin install pagerduty@pagerduty-claude-code-plugins. It's also in Anthropic's official plugin marketplace. The plugin bundles PagerDuty's hosted MCP server (https://mcp.pagerduty.com/mcp), which needs a PagerDuty API user token in the PAGERDUTY_API_KEY environment variable. Set it in .claude/settings.local.json for one repository, or in ~/.claude/settings.json for all of them, then restart Claude Code. Create the token in PagerDuty under User Settings > API Access. Good to know On its first run it maps the repository to a PagerDuty service: from a service name you pass, a saved .claude/risk-config.json, a Backstage catalog-info.yaml annotation, the repository's name, or by asking you. It reads your git diff and commit history locally. The skill builder needs enrollment in PagerDuty's Skills and Advance MCP/API Early Access programs, and the PagerDuty Advance MCP server.