← ClaudeAtlas

release-promotionlisted

Use this skill when promoting an image or chart version across environments (dev -> staging -> production), rolling back a promotion, or updating the version-pinning repo's digests. Don't use it for single-environment Helm deploys (use deployment) or code-level rollback (use refactor-plan).
atretyak1985/swarmery · ★ 3 · DevOps & Infrastructure · score 62
Install: claude install-skill atretyak1985/swarmery
# Purpose Promote the project's service images and chart versions across environments using immutable digests, producing updated entries in the version-pinning repo (if the project uses one -- project.json → repos; referenced below as `<versions-repo>`) with current/previous tracking for auditability and fast rollback. This skill manages the cross-environment promotion lifecycle; it defers the single-environment Helm upgrade execution to `deployment` and pull-based GitOps reconciliation to `gitops-promotion`. # When to use this skill - Trigger A -- Promoting an image from dev to staging or staging to production - Trigger B -- Rolling back a promotion to the previous known-good digest - Trigger C -- Updating `<versions-repo>` after a verified deployment - Trigger D -- Reviewing promotion history in Git for audit purposes - Trigger E -- Coordinating Helm chart version promotion alongside image digest promotion # When NOT to use this skill - Anti-trigger A -- Code-level refactoring rollback (git revert) -> use `refactor-plan` instead - Anti-trigger B -- Feature-flag toggles that change behavior without deploying a new image - Anti-trigger C -- Schema-only migrations that deploy without a new service image -> use `migration-check` instead - Anti-trigger D -- Hotfix cherry-picks that bypass the normal promotion queue -- handle as expedited single-repo deployments with post-hoc `<versions-repo>` update - Anti-trigger E -- Single-environment Helm upgrade orchestration -> use `d