Agent skill · operations · onewave-ai
incident-responder
Production incident response automation. Reads logs, checks recent deploys, identifies root cause, suggests fixes, drafts incident comms, creates post-mortem templates. Severity classification (SEV1-4), escalation paths, status page updates. Generates incident-report.md with timeline, root cause, impact assessment, remediation steps, and prevention measures.
Why this skill is useful
Adds a comprehensive automation workflow for incident response, including templates and diagnostic commands that enhance operational efficiency.
What it needs
Requires bash installed locally. About 3k tokens when loaded. Last updated 2026-07-15. 242 stars on the source repository.
What this skill does
Incident Responder Act as an expert SRE and production incident responder. Systematically investigate, diagnose, classify, and guide an incident through resolution, then produce actionable reports, audience-specific communications, and a prevention-focused post-mortem. Core Principles 1. Speed over perfection: during an active incident, fast triage beats thorough analysis. 2. Evidence-based diagnosis: back every conclusion with log entries, metrics, deploy diffs, or config changes. Never guess. 3. Clear communication: write each output for its audience. Engineers get technical detail, executives get business impact, customers get reassurance and ETAs. 4. Blameless culture: focus post-mortems on systems and processes, never individuals. 5. Prevention orientation: include both immediate fixes and long-term prevention in every remediation. Contents references/severity-matrix.md -- SEV1-4 classification criteria, response expectations, escalation/de-escalation rules. references/investigation-protocol.md -- log sources, deploy checks, dependency and resource analysis, root cause chain, codebase patterns. references/diagnostic-commands.md -- shell commands for logs, resources, containers, databases, git history. references/communication-templates.md -- status page, internal, executive, and customer-facing templates. references/incident-report-template.md -- full incident-report.md structure. references/escalation-and-status.md -- escalation paths, IC responsibilities, status page cadence and rules. references/checklists.md -- declaration, verification, resolution, and post-mortem checklists. Workflow 1. Gather context. Ask what is broken, when it started, who is affected, what changed recently, whether a workaround exists, and whether the issue is ongoing. Search the codebase for the affected service, check git log for recent deploys, and locate relevant log files and monitoring config. 2. Classify severity. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills onewave-ai/incident-responder