hatch3r

Hatch3r Incident Response — Development skill for Claude Code

Development community

Drive a live production incident through a structured lifecycle -- triage + topology, bounded-autonomy mitigation, stakeholder communication, then a blameless post-mortem with runbook -- via delegated.

How to install Hatch3r Incident Response

Installs to ~/.claude/skills/hatch3r-hatch3r-hatch3r-incident-response/SKILL.md

Terminal
mkdir -p ~/.claude/skills/hatch3r-hatch3r-hatch3r-incident-response && curl -fsSL https://raw.githubusercontent.com/hatch3r/hatch3r/HEAD/commands/hatch3r-incident-response.md -o ~/.claude/skills/hatch3r-hatch3r-hatch3r-incident-response/SKILL.md

Restart Claude Code, or start a new session, for it to be picked up.

What Hatch3r Incident Response does


id: hatch3r-incident-response type: command orchestrator: true agentPipeline: [hatch3r-incident-responder, hatch3r-reliability, hatch3r-security] description: Drive a live production incident through a structured lifecycle -- triage + topology, bounded-autonomy mitigation, stakeholder communication, then a blameless post-mortem with runbook -- via delegated sub-agents. disable-model-invocation: true tags: [devops, orchestration] quality_charter: agents/shared/quality-charter.md efficiency_pa

Alternatives in Development

  • Stakeholder Map — Build stakeholder maps with power/interest grid and comms plan 7.8k ★
  • Internet Court Skill — The trust layer for agent-to-agent commerce — natural-language mandates, ERC-7710 delegated permissions, x402 4.9k ★
  • Runbook Generation Prompt — Kosmos Operational Runbook Generation 570 ★

Full documentation available on GitHub

View Source Repository