Skip to content
Skills Library
DevOps & cloud · Automation

deploy

/deploy

Post-merge deployment workflow covering feature flags, canary/blue-green rollout, smoke-test verification, and rollback triggers. Use after a PR is merged and you need to ship it safely to production. Trigger on "deploy", "roll out", "canary", "feature flag", "rollback".

Repository
llms ↗
Licence
MIT
Last repository change
21.05.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
10
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 21.05.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Post-merge deployment workflow covering feature flags, canary/blue-green rollout, smoke-test verification, and rollback triggers. Use after a PR is merged and you need to ship it safely to production. Trigger on "deploy", "roll out", "canary", "feature flag", "rollback".

Triggers from the description

deployroll outcanaryfeature flagrollback
Original author description

Post-merge deployment workflow covering feature flags, canary/blue-green rollout, smoke-test verification, and rollback triggers. Use after a PR is merged and you need to ship it safely to production. Trigger on "deploy", "roll out", "canary", "feature flag", "rollback".

How it works

  1. Usage
  2. Workflow
  3. Template Locations
  4. Progressive Disclosure Rules
  5. Relationship to Other Skills
  6. Examples
  7. Gotchas
Original SKILL.md headings · 124 lines, 684 words
SKILL.md preview
---
name: deploy
description: Post-merge deployment workflow covering feature flags, canary/blue-green rollout, smoke-test verification, and rollback triggers. Use after a PR is merged and you need to ship it safely to production. Trigger on "deploy", "roll out", "canary", "feature flag", "rollback".
allowed-tools: Read, Grep, Glob, Bash, WebFetch, WebSearch
---

# Deploy — Post-Merge Deployment Workflow

Structured guidance for everything between `/pr-merge` (code merged) and `/ops` (long-term observability). Covers feature flags, gradual rollout, post-deploy verification, and rollback conditions. Auto-detects context from project signals or accepts explicit subcommand.

## Usage

```
/deploy              # Auto-detect from project signals
/deploy flags        # Explicit: feature flag setup (LaunchDarkly, Flipt, env-based)
/deploy canary       # Explicit: canary / blue-green gradual rollout
/deploy verify       # Explicit: post-deploy smoke tests and SLO gate
/deploy rollback     # Explicit: rollback trigger conditions and strategies
```

## Workflow

### Step 1: Determine Context

Parse `$ARGUMENTS` for explicit mode. If no arguments, run context detector:

```bash
DETECTED=$(bash "$HOME/.claude/skills/deploy/lib/context-detector.sh")
```

### Step 2: Show Relevant Guidance

Based on detected or explicit mode, use progressive disclosure:

**Level 1 — Summary** (default, ~15 lines):
Read and present the summary template. This is the entry point.

**Level 2 — Patterns** (on request, ~60 lines):
When the user asks for more detail, "show me patterns", code examples, or "Don't/Do/Best" style guidance, read the patterns template.

**Level 3 — Full SOP** (future):
Not yet available. Dive into patterns and answer specific questions instead.

### Step 3: Handle Multiple Contexts

If context-detector returns multiple modes (e.g., "verify,rollback"):

- Show summary for each detected mode
- Ask: "Which area do you want to dive deeper into?"

### Step 4: No Context Detected

If detection returns "none" and no explicit mode was given:

- Read and show `templates/overview.md`
- Let the user choose which mode to start with

## Template Locations

### Summary Templates (~15 lines each — L1 default)

| Mode       | File                                                    |
| ---------- | ------------------------------------------------------- |
| `flags`    | `~/.claude/skills/deploy/templates/flags/summary.md`    |
| `canary`   | `~/.claude/skills/deploy/templates/canary/summary.md`   |
| `verify`   | `~/.claude/skills/deploy/templates/verify/summary.md`   |
| `rollback` | `~/.claude/skills/deploy/templates/rollback/summary.md` |

### Patterns Templates (~60 lines each — L2 on request)

| Mode       | File                                                     |
| ---------- | -------------------------------------------------------- |
| `flags`    | `~/.claude/skills/deploy/templates/flags/patterns.md`    |
| `canary`   | `~/.claude/skills/deploy/templates/canary/patterns.md`   |
| `verify`   | `~/.claude/skills/deploy/templates/verify/patterns.md`   |
| `rollback` | `~/.claude/skills/deploy/templates/rollback/patterns.md` |

### Reference Templates

| Mode       | File                                            |
| ---------- | ----------------------------------------------- |
| `overview` | `~/.claude/skills/deploy/templates/overview.md` |

## Progressive Disclosure Rules

1. **Always start at L1** — never dump 300+ lines unprompted
2. **Read templates on demand** — use the Read tool to load templates, don't memorize content
3. **User drives depth** — "show me patterns", "give me code", "how do I set up X" triggers L2
4. **Cross-reference, don't duplicate** — for secrets in flags, cite `/security operations`; for post-deploy metrics, cite `/ops metrics`

## Relationship to Other Skills

- **`/pr-merge`**: Merge is the trigger. `/deploy` is the next step after the PR lands on main.
- **`/ops`**: Covers long-term observability (logging, metrics, dashboards, alerting). `/deploy verify` is the immediate post-deploy gate; `/ops` sets up the sustained monitoring layer.
- **`/security operations`**: Covers secrets management and deployment security. Use before configuring flag SDK credentials.
- **`/implementation`**: After implementing a flagged feature, use `/deploy flags` to wire the flag evaluation into the request path.

## Examples

**Auto-detected flags context** (launchdarkly in deps):

> → context-detector returns "flags"
> → Read and show `templates/flags/summary.md`
> → User: "show me the SDK patterns"
> → Read and show `templates/flags/patterns.md`

**Explicit canary request**:

> User: `/deploy canary`
> → Read and show `templates/canary/summary.md`

**No context, overview**:

> User: `/deploy`
> → context-detector returns "none"
> → Read and show `templates/overview.md`

**Post-merge verification flow**:

> PR merged → `/deploy verify` → smoke tests pass → promote to 100% traffic
> → if any check fails → `/deploy rollback`

## Gotchas

- Never roll back a DB migration without a tested down-migration — data loss risk. Stop traffic and escalate instead.
- Automatic rollback triggers on 5xx > 1% absolute, p99 > baseline × 1.5, or health endpoint non-200 — these fire without manual confirmation; know them before deploying.
- Flag-gated and canary rollbacks are instant (flip flag / drain traffic); only a full-deploy rollback needs `git revert + redeploy` (5–15 min) — pick the fastest path that applies.
- Every automatic rollback in production requires a post-mortem, and the rollback event must be logged (version numbers, trigger, timestamp).
Files in this package (10)
  • SKILL.md 6 KB
  • templates/overview.md 1 KB
  • templates/canary/patterns.md 2 KB
  • templates/canary/summary.md 1 KB
  • templates/flags/patterns.md 3 KB
  • templates/flags/summary.md 1 KB
  • templates/rollback/patterns.md 3 KB
  • templates/rollback/summary.md 2 KB
  • templates/verify/patterns.md 3 KB
  • templates/verify/summary.md 2 KB

Versions

RepositoryScoreLicence
This page · matteocervelli/llms100MIT
zeitlos/lucity100AGPL-3.0
jeremylongshore/tons-of-skills-marketplace100MIT
zeitlos/lucity100AGPL-3.0
microsoft/power-platform-skills100MIT
friendlyinternet/nuxt-crouton100MIT
wraith-proxy/wraith-skills100MIT
jikig-ai/soleur100Apache-2.0
curiositech/windags-skills100Apache-2.0

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version ff96437cb57a (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90deployment-strategies
    Gets a change into production safely — blue-green, canary, rolling, feature flags, and the rollback that makes each of them safe. Use this whenever the user is planning a release, asks how to deploy without downtime, mentions canary or blue-green, is adding a feature flag, or is…
  • 90safe-deployment
    Discipline for shipping changes reversibly, decouple deploy (code reaches production) from release (users see it) with feature flags, roll out progressively, and define the automated rollback trigger before shipping, not during the incident. Use when the user asks how to deploy…
  • 100blue-green-deploy
    Configure zero-downtime deployment strategies including blue-green, canary, and rolling deployments. Implement traffic shifting, health checks, and rollback procedures. Use when implementing production deployment strategies or zero-downtime releases.
  • 100release-plan
    Design a pre-deploy release and rollout strategy: pick the pattern (feature flag, canary, blue-green, or progressive delivery) by risk, then specify the exposure ramp, promotion metric and threshold, and rollback trigger. Designs the rollout, never executes it. Gated…
  • 100flyio-deploy-integration
    Plan a Fly.io rolling, canary, or blue-green release with health, capacity, storage, and rollback constraints. Use when a release needs progressive exposure. Trigger with: "canary deploy on Fly", "use Fly blue-green", "design Fly rollout".
  • 100blue-green-canary-deployments
    Designs and executes progressive delivery strategies — blue-green cutover, canary rollout, and traffic-shifted releases — with automated health checks and rollback triggers, typically on Kubernetes. Use when the user asks to "reduce deployment risk," "set up canary/blue-green…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.