kienbui1995/magic-powers/ado-release-management
Claude Code and agent skill by kienbui1995/magic-powers
Trust tier 3
- community
Source check pending
Checking that the SKILL.md file is still in the repository.
Use when implementing release management on Azure DevOps — deployment gates (quality gates), pre/post-deployment approvals, deployment rings, rollback strategies, deployment freeze windows, and multi-environment promotion.
Install
npx vskill@latest install kienbui1995/magic-powers/ado-release-managementSKILL.md
The same SKILL.md was published earlier as kienbui1995/magic-powers/ado-release-management.
ADO Release Management
When to Use
- Need quality gates before production deployment (smoke tests, monitor alerts)
- Implementing staged rollout (dev → staging → prod with approvals)
- Setting up deployment freeze windows for production
- Designing rollback strategy for failed deployments
- Implementing deployment rings (canary → early adopter → broad)
- Preventing concurrent deployments racing to the same environment
Core Jobs
1. Environment Approvals & Checks
Configure via UI: Pipelines → Environments → production → Approvals and checks:
- Approvals — add approvers (individuals or groups), set timeout, add instructions for approver
- Branch control — only allow deployment from
mainorrelease/*branches - Exclusive lock — only one deployment at a time (prevents concurrent deploy race conditions)
- Azure Monitor alerts — must have no active alerts before deploying (automated health gate)
2. Gates (Quality Gates)
YAML pipeline equivalent — environment checks:
3. Deployment Rings Pattern
4. Rollback Strategy
5. Deployment Freeze Windows
6. Multi-Environment Promotion Pattern
Key Concepts
- Deployment ring — subset of users/infrastructure receiving a deployment first (canary → early adopter → broad)
- Gate — automated quality check that must pass before/after deployment; polled on interval until pass or timeout
- Slot swap — Azure App Service feature to swap staging/production slots instantly (zero-downtime, instant rollback)
- Environment check — approval, branch control, exclusive lock, or automated check tied to a deployment environment
- Canary deployment — route a small percentage of traffic to the new version, validate metrics, then increase
- Blue/green deployment — maintain two identical environments; switch all traffic at load balancer level
- Exclusive lock — only one pipeline run can deploy to an environment at a time; others queue or fail
Checklist
- [ ] Every production deployment requires at least one human approval?
- [ ] Branch control check prevents non-main branches from deploying to production?
- [ ] Rollback procedure documented, tested, and runnable (not just written in Confluence)?
- [ ] Post-deployment smoke test validates key user journeys (not just HTTP 200)?
- [ ] Exclusive lock on production environment (prevents concurrent deployments)?
- [ ] Deployment freeze windows enforced via checks (not just Slack messages)?
- [ ] Deployment ring strategy defined for high-risk changes?
Key Outputs
- Multi-environment pipeline with approval gates and automated checks on production
- Automated quality checks (Azure Monitor, smoke tests) before production deploy
- Rollback procedure runnable from pipeline (not manual steps only)
- Deployment rings for progressive rollout of high-risk or high-traffic changes
Output Format
- 🔴 Critical — no approvals on production environment, no rollback strategy defined, any branch can trigger production deployment
- 🟡 Warning — manual-only quality checks with no automated gates, no exclusive lock configured (concurrent deploy risk), rollback requires manual steps not covered in runbook
- 🟢 Suggestion — add Azure Monitor gate for automated health validation, implement slot swap for zero-downtime instant rollback, use deployment rings for services with large user base
Anti-Patterns
- Approval-only gates without automated checks (human approvers cannot verify system health metrics at approval time)
- Rollback not tested in staging (rollback procedure fails in production when needed most)
- Bypassing approval "just this once" without audit trail — document any bypass in the work item or change log
- Deploying to all environments simultaneously instead of sequentially (no staged validation opportunity)
- Classic release pipelines for new work (not version-controlled, harder to review and audit than YAML)
Integration
ado-pipeline-design— the multi-stage pipeline structure that release management builds uponado-pipeline-optimization— optimize the build pipeline that feeds into the releaseado-pipelines-ops— environments and approval infrastructure setup (creating environments, adding checks via UI)
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/ado-release-management/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/kienbui1995/magic-powers/ado-release-management)