PagerDuty Pre-Commit Risk Score

Hook into your git workflow and get a risk score before you commit. The tool reads your pending diff, calls the PagerDuty API to pull incident records for the last 90 days, and maps incident metadata to the files and services your diff touches. It parses incident summaries, deduplicates by service and file path, and produces a numeric risk score plus a short breakdown: which files are linked to recent outages, how many incidents, when the last incident occurred, and whether any incidents are still marked active or unresolved.

The plugin runs locally as a pre-commit or pre-push check, authenticates with your PagerDuty account, and caches recent incident data for speed. It flags high-risk hunks inline with your diff and outputs a concise report you can read in CI logs or your terminal. It also offers a JSON output you can pipe into other tools and a threshold you can fail builds on if the risk score exceeds your policy.

Imagine fixing a config change that touches an auth module and seeing an immediate alert: three incidents in the last 30 days tied to that module, last incident still open — abort the commit and open a patch request instead. That saves you from toggling between the terminal, the PagerDuty site, and your repo UI to cross-check history, and it prevents deployments that would trigger on-call pages.