Skill

incident

Run incident triage and mitigation with deterministic logging and optional rollback via the configured deploy adapter.

Install

npx claudepluginhub bishnubista/stacklane --plugin stacklane

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Use the script entrypoint to create incident artifacts and execute controlled mitigation.

SKILL.md

Similar Skills

using-git-worktrees

Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.

superpowers

168.3k

subagent-driven-development

3 files

Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.

superpowers

168.3k

dispatching-parallel-agents

Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.

superpowers

168.3k

Stats

Stars0

Forks0

Last CommitFeb 9, 2026

Actions

View Source View Plugin View on GitHub View README

/stacklane:incident

Use the script entrypoint to create incident artifacts and execute controlled mitigation.

Command

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 rollback is requested in production, require confirmation token.

If --healthcheck-url is provided, it must be an absolute http:// or https:// URL.

Return the incident document path and any rollback result.

Boundaries

Focus on containment and recovery actions.

Keep broader process follow-ups in plangate.

/stacklane:incident

Use the script entrypoint to create incident artifacts and execute controlled mitigation.

Command

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 rollback is requested in production, require confirmation token.
If --healthcheck-url is provided, it must be an absolute http:// or https:// URL.
Return the incident document path and any rollback result.

Boundaries

Focus on containment and recovery actions.
Keep broader process follow-ups in plangate.