/stacklane:incident
Use the script entrypoint to create incident artifacts and execute controlled mitigation.
Command
bash
bash "${CLAUDE_PLUGIN_ROOT}/scripts/stacklane-incident.sh" --environment production --name incident
Optional Flags
- •
--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
Execution Rules
- •Always create an incident record in
.stacklane/incidents/. - •Always collect logs unless no logs command is configured.
- •If
--mitigation rollbackis requested in production, require confirmation token. - •If
--healthcheck-urlis provided, it must be an absolutehttp://orhttps://URL. - •Return the incident document path and any rollback result.
Boundaries
- •Focus on containment and recovery actions.
- •Keep broader process follow-ups in plangate.