From deployment-rollback-manager
This skill manages and executes deployment rollbacks with safety checks. It helps ensure smooth recovery from failed deployments by automating the rollback process. Use this skill when a deployment has issues, such as errors, performance degradation, or unexpected behavior. The skill is triggered by requests to "rollback deployment", "revert to previous version", or similar phrases related to deployment recovery. It prioritizes safe rollback procedures and provides options for verification.
How this skill is triggered — by the user, by Claude, or both
Slash command
/deployment-rollback-manager:deployment-rollback-managerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill enables Claude to manage and execute deployment rollbacks, ensuring a stable and reliable system. It automates the process of reverting to a previous, known-good deployment state, minimizing downtime and potential disruptions.
This skill enables Claude to manage and execute deployment rollbacks, ensuring a stable and reliable system. It automates the process of reverting to a previous, known-good deployment state, minimizing downtime and potential disruptions.
This skill activates when you need to:
User request: "Rollback deployment to the previous stable version due to errors."
The skill will:
rollback-deploy command.User request: "Revert to the last known good deployment. Performance has degraded significantly since the last update."
The skill will:
rollback-deploy command.This skill can be used in conjunction with other monitoring and alerting tools to automatically trigger rollbacks when issues are detected. It also integrates with deployment pipelines for automated rollback execution.
3plugins reuse this skill
First indexed Jul 13, 2026
npx claudepluginhub dorucioclea/claude-code-plugins-plus --plugin deployment-rollback-managerGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.