How do I install the Release And Deployment skill?

Run npx skillmds add majiayu000/release-and-deployment in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Release And Deployment safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Release And Deployment?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Release And Deployment free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Release And Deployment?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Release And Deployment by majiayu000

Name: Release And Deployment
Rating: 4.2 (5 reviews)
Author: majiayu000

Release And Deployment

Ships changes safely and often — pipelines, deployment strategies, feature flags, rollback, and database changes. Use this to design a deployment pipeline, reduce release risk, roll out a risky change gradually, plan a schema migration, or work out why releases are infrequent and frightening.

majiayu000 99c7654 2 files · 4.4 KB Updated Sep 9, 2026 567 repo stars

File contents

Release and deployment

Release risk is dominated by batch size. Large infrequent releases are dangerous because many changes land at once and nobody can tell which one broke it — so teams release less often, which makes each release larger. The loop is the problem.

Separate deploy from release

Deploying code and exposing behavior to users are different acts, and coupling them forces every deployment to be a business decision.

Decouple with flags: deploy continuously, expose deliberately. This makes rollback a configuration change rather than a redeployment, which is the difference between seconds and minutes at the worst possible time.

Flags are inventory and rot. Give each an owner and a removal date; a codebase full of stale flags has combinatorial states nobody has tested.

The pipeline is the quality gate

Automate everything between commit and production, and let the pipeline reject. Manual steps get skipped under pressure, which is exactly when they matter.

Order gates fast-to-slow so failure is cheap: lint and unit tests, then integration, then anything requiring a deployed environment. A pipeline slow enough to be circumvented is worse than a fast one with fewer checks, because it will be circumvented.

Build once and promote the same artifact through environments. Rebuilding per environment means the thing you tested is not the thing you shipped.

Roll out gradually

Expose to a small population first and watch real signals before widening. Canary or percentage rollout turns a total failure into a contained one.

Define the abort condition before starting, with a threshold and a named decision-maker. Under pressure, and with the change fresh, the instinct is always to wait a little longer and see.

Database changes are the asymmetric risk

Code rolls back; data does not. Make schema changes backward-compatible and multi-step: add the new structure, write to both, migrate, switch reads, then remove the old — with the application tolerant of both shapes throughout.

Test the migration against production-scale data. A migration that is instant on a development dataset can lock a large table for a length of time nobody modeled.

Never

Couple deploying code to exposing behavior.
Promote a different artifact than the one that was tested.
Begin a rollout without a defined abort condition.
Ship a schema change that requires the application and database to deploy simultaneously.

---name: release-and-deploymentdescription: Ships changes safely and often — pipelines, deployment strategies, feature flags, rollback, and database changes. Use this to design a deployment pipeline, reduce release risk, roll out a risky change gradually, plan a schema migration, or work out why releases are infrequent and frightening.--- # Release and deployment Release risk is dominated by batch size. Large infrequent releases are dangerous because many changes land at once and nobody can tell which one broke it — so teams release less often, which makes each release larger. The loop is the problem. ## Separate deploy from release Deploying code and exposing behavior to users are different acts, and coupling them forces every deployment to be a business decision. Decouple with flags: deploy continuously, expose deliberately. This makes rollback a configuration change rather than a redeployment, which is the difference between seconds and minutes at the worst possible time. Flags are inventory and rot. Give each an owner and a removal date; a codebase full of stale flags has combinatorial states nobody has tested. ## The pipeline is the quality gate Automate everything between commit and production, and let the pipeline reject. Manual steps get skipped under pressure, which is exactly when they matter. Order gates fast-to-slow so failure is cheap: lint and unit tests, then integration, then anything requiring a deployed environment. A pipeline slow enough to be circumvented is worse than a fast one with fewer checks, because it will be circumvented. Build once and promote the same artifact through environments. Rebuilding per environment means the thing you tested is not the thing you shipped. ## Roll out gradually Expose to a small population first and watch real signals before widening. Canary or percentage rollout turns a total failure into a contained one. Define the abort condition **before** starting, with a threshold and a named decision-maker. Under pressure, and with the change fresh, the instinct is always to wait a little longer and see. ## Database changes are the asymmetric risk Code rolls back; data does not. Make schema changes backward-compatible and multi-step: add the new structure, write to both, migrate, switch reads, then remove the old — with the application tolerant of both shapes throughout. Test the migration against production-scale data. A migration that is instant on a development dataset can lock a large table for a length of time nobody modeled. ## Never - Couple deploying code to exposing behavior. - Promote a different artifact than the one that was tested. - Begin a rollout without a defined abort condition. - Ship a schema change that requires the application and database to deploy simultaneously.

Frequently asked questions