mcpbeat

Deploy Release

hoangnguyen0403/deploy-release

Prepare and verify a staged or production deployment with rollback and smoke checks.

655 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
536
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/HoangNguyen0403/agent-skills-standard --skill deploy-release

The instruction itself

8 sections, as written by the author

Deploy Release Skill

> [!IMPORTANT]

> Prepare and verify a staged or production deployment with rollback and smoke checks.

Optional args: slug=<feature>, ticket=<id/url>, mode=interactive|autonomous|channel, channel=<id>, auto_continue=true|false, profile=business|hybrid|technical.

Instructions

When the user asks to perform this workflow, execute the following steps:

Deploy Release Workflow

Goal: Ship verified work with explicit deployment steps, smoke checks, and rollback criteria.

Steps

  • Confirm readiness:
  • Verification report is PASS or accepted with documented risk.
  • Required approvals are present.
  • Migrations and feature flags are accounted for.
  • Prepare release:
  • Identify version, environment, deploy command, and owner.
  • Confirm secrets, config, queues, cron, and external services.
  • Define rollback command or revert path.
  • Deploy:
  • Run staging deploy first when available.
  • Run smoke checks before promotion.
  • Promote only when smoke checks pass.
  • Monitor:
  • Check logs, metrics, errors, latency, and core user flows.
  • Stop or roll back on defined failure signals.
  • Route:
  • User-facing notes -> publish-notes.
  • Process and standards feedback -> retro-learn.

Runtime Contract

  • Use once verification/UAT signoff is PASS and a release window is open.
  • Required inputs: verification report plus release version, environment, and rollback path.
  • Return BLOCKED only when required approvals, migrations, or rollback path are unresolved.

Handoff Payload

  • slug, release verdict (GO/NO-GO/ROLLED-BACK), smoke check results, rollback path, outcome report, next workflow.

Blocking Questions

  • Ask max 3 at a time with a recommended default and 2-3 options.

Output Template

# Deployment Report: [Name]

## Release Verdict
GO | NO-GO | ROLLED-BACK

## Release

## Environments

## Commands

## Smoke Checks

| Check | Result | Evidence |
| --- | --- | --- |
| [check] | [PASS/FAIL/BLOCKED] | [evidence] |

## Rollback

## Outcome Report
feature_status: implemented | blocked
requirement_trace: BRD-OBJ-* -> REQ-* -> AC-* -> SRS-* -> evidence
completed_evidence: []; missing_evidence: []; decision_needed: []; recommended_next_workflow: publish-notes | retro-learn

## Next Workflow

publish-notes | retro-learn

## Cost Report
Call `get_session_cost(workflow="deploy-release")` before final handoff.

How to use it

Copy the folder

Take hoangnguyen0403/deploy-release from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.