A deployment-phase workflow that prepares and, after approval, carries out a software release. It records the target, changed services, migrations, feature flags, rollback plan, affected systems, and verification details.

Use it after testing has passed to prepare a deployment proposal, request human approval, execute the approved release under supervision, and record the result in deployment artifacts or configured tickets.

It makes release risks and recovery steps explicit before code reaches an environment. It also ensures deployment is approved by a person rather than happening automatically.

deploy — Skill for Claude Code by lantisprime/claude-sdlc

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/lantisprime/claude-sdlc

agentmods

npx agentmods add skills/lantisprime/claude-sdlc/deploy

Made for: Claude Code.

Or install sdlc-plugin, the plugin that ships this one along with the rest of its 18 skills, 16 commands, 10 agents, 4 hooks.

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/lantisprime/claude-sdlc/deploy/github.svg)](https://agentmods.dev/skills/lantisprime/claude-sdlc/deploy)

Your own site

<a href="https://agentmods.dev/skills/lantisprime/claude-sdlc/deploy"><img src="https://agentmods.dev/badge/skills/lantisprime/claude-sdlc/deploy/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/lantisprime/claude-sdlc/deploy"><img src="https://agentmods.dev/badge/skills/lantisprime/claude-sdlc/deploy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 773 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.00091	$0.00773
Opus 5.5	$0.00036	$0.00309
Sonnet 5.5	$0.00018	$0.00155
Haiku 4.5	$0.00009	$0.00077

Measured 1mo ago against content hash db7a89ff63cc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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.

skills/deploy/SKILL.md · 87 lines

How it starts

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

Deploy (Phase 6)

Release code that has passed Test — under explicit human approval.

Prerequisite

.claude/sdlc/gates/test-<task-slug>.md must exist and be signed. Without it, this skill refuses to run.

Step 1 — Propose the deployment

Produce a deployment proposal, not a deployment. Include:

Target environment (dev / staging / production)
Commit SHA / tag / image reference
Changed files and services
DB migrations? (yes/no, reversible?)
Feature flags? (default state)
Rollback plan
Blast radius (users/services affected)
Deployment window / maintenance window if applicable

Step 2 — Human approval gate

This is non-negotiable. Deployments never auto-execute. Ask the human to confirm the proposal. Record the approval at .claude/sdlc/gates/deploy-<task-slug>.md with timestamp and approver.

Step 3 — Execute (under human supervision)

Execute the deployment via the configured pipeline/runbook. Stream output. Halt on the first error and ask for direction — do not retry automatically.

Step 4 — Record

Update the ticket(s) with:

Commit SHA, environment, timestamp, approver
Link to pipeline run / deployment log
Post-deploy verification results (smoke tests)

Detection:

GitHub/GitLab Issues via .claude/sdlc/env.json → comment on the issue
Jira/Linear via MCP → transition to "Deployed" (or equivalent) with a comment
None configured → write .claude/sdlc/deployments/<YYYY-MM-DD>-<task-slug>.md (or .json if configured)

Step 5 — Post-deploy verification

Run the smoke-test subset of the test suite against the deployed environment. If any fail:

Execute the rollback from Step 1
Log a defect (see test skill)
Do not mark the deployment complete

What this skill must NEVER do

Auto-execute a deployment.
Skip the rollback plan.
Close a ticket before post-deploy verification passes.
Deploy code that does not have a signed test gate.

References

templates/deployment.md
templates/gate.md
docs/SDLC.md Deploy

Read the full file on GitHub · 87 lines

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.

1mo ago First seen · 87 lines · 91 tokens per session scan A db7a89ff63cc

Subscribe to this mod's changes

deploy is a skill published in the GitHub repository lantisprime/claude-sdlc (3 stars, last pushed 6mo ago), licensed MIT. It adds 91 tokens to every session and 773 once invoked, about $0.0004 per session on Opus 5.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-08-31.

Claude Code DevOps and cloud Git and workflow Releases agent-framework agentic-coding agentic-workflow claude-ai claude-code-plugin

gh-cli

GitHub CLI (gh) reference for repos, issues, PRs, Actions, releases, gists, projects, codespaces, and the API.

HigorAlves/orc · 33 tokens

release-management

Cut a semver release from conventional commits — bump, grouped changelog, annotated tag, GitHub release.

HigorAlves/orc · 24 tokens

merge-and-release

Reference document describing merge prerequisites (approval, CI checks, mergeable, conversations resolved, stale approval), release versioning (semantic semver), and changelog generation. Explains why Tier 3 confirmation is structural: merge and release cost is borne by downstream people. Reference only…

synaptiai/synapti-marketplace · 82 tokens

codex-changelog

This skill should be used when the user asks to check for new Codex CLI (codex-cli) releases, "what changed in Codex", "any Codex updates", "check codex releases", "diff the codex version", or wants Codex CLI releases reviewed for changes relevant to THIS repo's Codex bridge. Reads a locally-stored last-checked…

zeikar/hyperclaude · 129 tokens

git-workflow

Enforces the release-branch Git model: scaffold feature branches, open PRs with review checks, cut releases with tags, and view workflow reference.

RealDougEubanks/ClaudeMarketplace · 34 tokens

changelog-generator

Generates a structured CHANGELOG.md following Keep a Changelog format from git history and ABD handoff artifacts. Prepends new version sections to existing changelogs.

RealDougEubanks/ClaudeMarketplace · 37 tokens