CodepitSee incident risk before you commit
Claude checks your changes against your service's PagerDuty incident history and scores the risk from 0 to 5. A second command builds skills for PagerDuty's SRE Agent.
Scan in CodepitScan checks all of PagerDuty/claude-code-plugins on your computer, before anything installs.
Codepit runs on your computer. Open this page there to scan it before installing.
PagerDutyMade by PagerDuty
7Stars on GitHubStars
Apache-2.0License
30 OctLast update
What you get
Run /pagerduty:pre-commit-risk-scoring with uncommitted changes, or add --branch to assess every commit on your branch. The assessment covers:
- Active incidents
- 90 days of incident history
- Changed files and risk signals
- Overlap with past incidents
- Risk score from 0 to 5
- Recommendations
Before you start
- Claude Code v1.0.33 or later.
- A PagerDuty API user token (User Settings > API Access in PagerDuty), set as
PAGERDUTY_API_KEYin your Claude Code settings. Restart Claude Code after adding it. - For the skill builder: enrollment in two PagerDuty Early Access programs, Skills and Advance MCP/API.
Try saying
Claude finds the base branch, matches the repo to a PagerDuty service, pulls its incidents and change events, and scores the whole branch the way a reviewer would see it.
Worth knowing
The plugin talks to PagerDuty's hosted MCP server at mcp.pagerduty.com with your API token, to read services, incidents and change events. Git history is read from your local repository.
On first run it saves which PagerDuty service your repo maps to in .pagerduty/pagerduty-risk-config.json in the repo. Delete that file to pick another service.
The skill builder is Early Access. Skills it creates go live in your PagerDuty account right away, and updating one replaces it completely.
Comes with a skill builder
/pagerduty:create-pagerduty-skill interviews you about a procedure, then writes it as a skill for PagerDuty's SRE Agent and deploys it.
- create-pagerduty-skill
