release

Agent Skills › di-sukharev/vibe › release

release

GitHub

执行生产环境部署流程，包括检查前置条件、运行本地门禁测试、审查并应用Terraform计划、执行发布及发布后验证。仅在用户明确请求时触发，确保部署安全与可追溯。

.agents/skills/release/SKILL.md di-sukharev/vibe

Trigger Scenarios

用户明确要求部署或发布应用需要执行生产环境上线操作

Install

npx skills add di-sukharev/vibe --skill release -g -y

More Options

Non-standard path

npx skills add https://github.com/di-sukharev/vibe/tree/master/.agents/skills/release -g -y

Use without installing

npx skills use di-sukharev/vibe@release

指定 Agent (Claude Code)

npx skills add di-sukharev/vibe --skill release -a claude-code -g -y

安装 repo 全部 skill

npx skills add di-sukharev/vibe --all -g -y

预览 repo 内 skill

npx skills add di-sukharev/vibe --list

SKILL.md

Frontmatter

{
    "name": "release",
    "description": "Runs a production deployment through scripts\/infra.mjs — preconditions, local gates, a reviewed Terraform plan and apply, the release, and post-release verification. Use only on an explicit user request to deploy or release."
}

Steps

Check preconditions; stop and report if any is missing:
- an explicit request to deploy or release;
- the hosting chosen in CHECKLIST;
- a clean tree (git status) and the branch pushed;
- a clear release commit.
Run the local gates: bun run check and bun run test:terraform, plus any e2e or smoke test the DEPLOYMENT or provider guide calls for.
Run bun run infra:plan -- <provider> and review the plan with the user. A destroy or a replace needs an exact --allow-destroy=<address> for that reviewed resource; stop and ask first. Apply only with bun run infra:apply -- <provider>. Never run raw terraform apply, -target, or state edits. If a release-root plan stops with run infra:apply to refresh the foundation outputs, follow DEPLOYMENT.
On the first release only, pass the admin seed through the environment as DEPLOYMENT describes. Never print ADMIN_SEED_EMAIL or ADMIN_SEED_PASSWORD.
Run bun run release -- <provider> --dry-run, then bun run release -- <provider>.
After the release, check /health/ready, the logs, run a sign-in smoke test, and confirm the deployed version.
Recovery: follow DEPLOYMENT — roll back with a new commit and a normal release, never a mutable tag; migrations only go forward.
Report to the user in plain words. Never print secrets or tfvars values.