pagerduty-incident-response
reference corpus · status live · domain OPS (Operations and SRE) · lane A · refresh pinned · tags GLOBAL · INCIDENT-RESPONSE · ON-CALL · RUNBOOKS · SRE · POSTMORTEM
What an agent uses it for
An agent writing on-call runbooks or incident-response automation queries this for severity levels, responder roles, and postmortem process.
curl -fsSLO https://raw.githubusercontent.com/xerj-org/xerj/corpus-hub/tools/xerj-code/hub/pagerduty-incident-response.jsonxerj corpus add --from ./pagerduty-incident-response.jsonxerj corpus index pagerduty-incident-response then xerj code pagerduty-incident-response "your question"Needs the xerj CLI and a local node running; the copy prompt covers both, checks each step, and shows how to stop only the node you started. No shell: the MCP tool xerj_code_search with corpus: "pagerduty-incident-response", once the corpus is indexed on the node.
Sources and pins
| source | pin | licence | size | review note |
|---|---|---|---|---|
| incident-response-docs | 464fc9d3e47e | Apache-2.0 | 170.4 MB / 216 files | Read LICENSE via authenticated GitHub API: 'Copyright 2016 PagerDuty, Inc.' + standard Apache-2.0 text, SPDX Apache-2.0; repo live. Keep LICENSE/NOTICE; ~165MB repo includes site assets/translations, filter to docs/ markdown. |
170.4 MB across 216 files. Added 2026-10-13.
Rights
Apache-2.0. Redistribution permitted with attribution per the licence review. The review block records a human opening each licence file at the pin. Detector output is a hint, never the verdict.
Retrieval spot-check (G7)
Not yet spot-checked. Queries are pre-registered in the registry before grading.