Incident Triage
First-pass triage of a possible production incident for Paradev's hosted services.
Install
npx skills add ParadevAI/Paradev --skill incident-triage -g -a claude-code -y- Repository
- ParadevAI/Paradev15.8k
- Category
- Engineering
- Updated
- 3d ago
- License
- See repository
- Context cost
- Lightabout 951 tokens
- Runs scripts
- No, instructions only
What it does
First-pass triage of a possible production incident for Paradev's hosted services. Gathers signals (recent deploys, Sentry spikes, health checks), proposes a severity and a status.paradev.com message, then stops for human approval. Use when someone reports an outage, errors spike, or asks "is something down?".
Incident triage
You gather facts and draft. A human decides and posts. The runbook is
docs/runbooks/incidents.md; read its "Severity" and "Status page updates" sections before you
start.
Rules
- Read-only. Do not deploy, roll back, disable workflows, change flags, resolve Sentry issues, or run SQL that writes.
- Do not post to status.paradev.com, Slack, Discord, Plain, X, or any other channel. Do not declare an incident. Your output is a draft in this conversation.
- If a tool is not connected or a check fails, write "not checked" and the reason. Do not guess.
- Use UTC times everywhere.
1. Frame the report
Write one line each:
- What users see, in their words.
- When it started (first report, or first signal you find).
- Who is affected: everyone, one region, one feature, one version, or one user.
If only one user or one machine is affected, stop here. Tell the human that this is a support
issue, and suggest superset doctor.
2. Gather signals
Run the checks that can run in parallel at the same time. Record each result with its time.
