A post-merge guide for releasing code to production safely, including gradual rollouts, checks after release, and rollback decisions.

Use it after a pull request is merged to set up feature flags, run canary or blue-green releases, verify the deployment, or plan a rollback.

It helps reduce the risk of sending a broken change to every user at once and makes recovery conditions clearer.

How matteocervelli/llms configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to matteocervelli/llms. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/matteocervelli/llms/main/.claude/skills/deploy/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/matteocervelli/llms

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/matteocervelli/llms/deploy.svg)](https://agentmods.dev/skills/matteocervelli/llms/deploy)

Your own site

<a href="https://agentmods.dev/skills/matteocervelli/llms/deploy"><img src="https://agentmods.dev/badge/skills/matteocervelli/llms/deploy.svg" alt="Measured on agentmods" height="20"></a>

Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,333 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00062	$0.01333
Opus 5	$0.00031	$0.00666
Sonnet 5	$0.00012	$0.00267
Haiku 4.5	$0.00006	$0.00133

Measured 3d ago against content hash f65e1e3af345, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

deploy scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/deploy/SKILL.md · 129 lines

How it starts

The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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:

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`

Read the full file on GitHub · 129 lines

Files

What ships with it

9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

3d ago First seen · 129 lines · 62 tokens per session scan A f65e1e3af345

Subscribe to this mod's changes

deploy is a skill published in the GitHub repository matteocervelli/llms (25 stars, last pushed 3mo ago), licensed MIT. It adds 62 tokens to every session and 1,333 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

CI and CD DevOps and cloud

import-prom-rule

Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…

ccfos/nightingale · 125 tokens

chinese-git-workflow

A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.

jnMetaCode/superpowers-zh · 69 tokens

configure-env-variables

Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…

microsoft/power-platform-skills · 119 tokens

atmos-cache

Atmos caching: CI cache configuration and commands, GitHub Actions cache integration, Terraform registry cache mirror/list/prune/stats/trust, and cache modernization guidance.

cloudposse/atmos · 35 tokens

atmos-profiles

Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.