release-management

Plan and govern software releases with versioned rollout and rollback capabilities.

Updated Oct 31, 2024
One-click install
npx skills add https://github.com/thesammykins/dotfiles --skill release-management-thesammykins
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-management
Source: https://github.com/thesammykins/dotfiles/tree/main/.agents/skills/release-management
Command: npx skills add https://github.com/thesammykins/dotfiles --skill release-management-thesammykins

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning and governing software releases with versioned rollout, rollback, and change control to reduce risk and downtime.

Core Features & Use Cases

  • Release planning & versioning: Create release notes, tag versions, and coordinate approvals.
  • Deployment strategy guidance: Define blue/green, canary, or rolling deployments with gates.
  • Rollback preparation: Pre-stage rollback artifacts and switchback steps for safe recovery.
  • Auditable change control: Enforce change-control artifacts and documentation across environments.

Quick Start

Run the release-management agent against your repository to plan, version, and deploy safely.

Frequently Asked Questions about release-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan a software release with rollback capabilities?

Plan software releases with rollback capabilities by pre-staging rollback artifacts, defining switchback steps, and coordinating approvals to ensure safe recovery and reduce downtime.

What is the best way to implement canary and blue-green deployment strategies?

Implement canary and blue-green deployment strategies by defining gated rollout phases across multiple environments, ensuring controlled traffic shifting and safe release coordination.

How do I maintain auditable change control for versioned rollouts?

Maintain auditable change control for versioned rollouts by enforcing change-control artifacts, generating release notes, tagging versions, and documenting switchback steps across all environments.

Do I need pre-staged rollback artifacts for a rolling deployment?

Pre-staged rollback artifacts are needed for rolling deployments to execute immediate switchback steps, ensuring safe recovery and minimizing downtime during versioned rollout failures.

When should I use a canary deployment instead of a blue-green strategy?

Use a canary deployment to validate changes with a small subset of traffic before a full rollout, whereas a blue-green strategy switches traffic between two identical environments for immediate rollback.