deployment

Releases tested code with versioning, staged rollout, smoke checks, and rollback paths.

4|Updated Jun 19, 2026
One-click install
npx skills add https://github.com/douglance/sdlc-plugin --skill deployment-douglance
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deployment
Source: https://github.com/douglance/sdlc-plugin/tree/main/.rulesync/skills/deployment
Command: npx skills add https://github.com/douglance/sdlc-plugin --skill deployment-douglance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping code to production is risky when releases lack traceable versions, verified health checks, or a way back when something breaks. This Skill structures the deployment phase so every release is tagged, smoke-tested against the live target, and paired with a ready rollback path. ## Core Features & Use Cases - Release Loop: Confirms green builds for the exact commit, tags the version, rolls out (preferring staged or canary releases), and runs smoke checks against the live system. - Rollback-First Discipline: Defines the down path (previous version, feature flag, or revert) before pushing the up path, and rolls back instead of debugging in production. - Config and Secrets Safety: Verifies environment config is correct for the target and keeps secrets out of artifacts, logs, and version control. - Use Case: After tests pass on a release candidate, use this Skill to tag v1.4.2, canary-deploy to production, run an end-to-end smoke probe, and record the exact rollback command in case the check fails. ## Quick Start Use the deployment skill to release the tested build to production with a version tag, smoke check, and rollback plan.

Frequently Asked Questions about deployment

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

FAQPage Schema
How do I deploy code safely to production?▼

Follow the release loop: confirm the build and tests are green for the exact commit, tag the version, roll out with staged or canary deployment where supported, and run smoke checks against the live target before declaring the release done.

What is a smoke check in a deployment?▼

A smoke check is a minimal end-to-end probe of the live system after rollout, not just confirmation that the process started. A release is only done when the smoke check proves the deployed version is healthy.

How do I roll back a failed deployment?▼

Define the rollback path before deploying: restore the previous version, toggle a feature flag, or revert the change. If smoke checks fail, roll back immediately rather than debugging in production.

Should I use canary or big-bang deployment?▼

Prefer staged or canary rollouts over big-bang releases wherever the target platform supports them. Gradual rollout limits blast radius and lets smoke checks catch problems before full exposure.

How do I handle secrets during deployment?▼

Verify environment config and secrets are correct for the target before rollout. Secrets must never land in the build artifact, logs, or version control.