Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From stacklane
Run incident triage and mitigation with deterministic logging and optional rollback via the configured deploy adapter.
npx claudepluginhub bishnubista/stacklane --plugin stacklaneHow this skill is triggered — by the user, by Claude, or both
Slash command
/stacklane:incidentThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use the script entrypoint to create incident artifacts and execute controlled mitigation.
Executes structured production incident response: triages P1-P3 severity, contains blast radius (rollback, mitigation), root-causes after stabilization, logs timeline, generates postmortem. Triggers on outages or 'incident'.
Handle production incidents with structured triage, mitigation, and post-mortem. Use when responding to production issues, outages, or security incidents.
Manages incident lifecycle with three modes: new (triage, communicate, mitigate), update (status update), and postmortem (blameless RCA report).
Share bugs, ideas, or general feedback.
Use the script entrypoint to create incident artifacts and execute controlled mitigation.
bash "${CLAUDE_PLUGIN_ROOT}/scripts/stacklane-incident.sh" --environment production --name incident
--name <short-name>--environment <name>--service <name>--severity <SEV0|SEV1|SEV2|SEV3>--mitigation <none|rollback>--rollback-target <deployment-id>--confirm-production I_UNDERSTAND_PRODUCTION (required for production rollback)--healthcheck-url <url>--dry-run.stacklane/incidents/.--mitigation rollback is requested in production, require confirmation token.--healthcheck-url is provided, it must be an absolute http:// or https:// URL.