deploy
Use when the user wants to release, deploy, rollback, or verify a deployment pipeline. Covers CI/CD gates, environment checks, canary/blue-green, and post-deploy smoke tests.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- deploy
- triggers
- [ "user" ]
- description
- Use when the user wants to release, deploy, rollback, or verify a deployment pipeline. Covers CI/CD gates, environment checks, canary/blue-green, and post-deploy smoke tests.
03 SKILL.md 正文
Deploy
Deploy, release, and verify code in target environments.
When to use
- User asks to deploy, release, or promote to staging/production.
- Rollback is needed.
- Post-deploy smoke tests or health checks are required.
- Need to choose between canary, blue-green, or simple rollout.
Core protocol
- Confirm artifact. Verify that the build/test/lint gates passed before deploy.
- Check environment. Read deployment config, secrets, and target infrastructure.
- Choose strategy. Canary, blue-green, rolling, or all-at-once based on risk.
- Execute deploy. Use the project's deployment command (e.g.,
npm run deploy,docker compose up,kubectl apply,gh workflow run). - Run smoke tests. Hit health endpoints, run critical e2e checks.
- Verify and report. Confirm success or trigger rollback.
See also
docker— container build, run, and compose.deploy— release orchestration, rollback, and smoke tests.git-github-adaptive-engineering- release flow selection,gh workflow run, environments, andgh release/attestation depth.
Output rule
- After deploy, run smoke tests and report: URL, version, status, rollback command.
- If rollback is needed, run it and verify the previous version is healthy.
04 同仓库更多 Skills
montador-de-ideias
Use when assembling, expanding, or elevating a raw project idea or initial prompt into an ultra-detailed, first-principles dossier and compiled master prompt with journalistic OSINT market research, Tech Lead and Staff Architect justifications, atomic and modular hardening/optimization, and high-impact contact surfaces.
git-github-adaptive-engineering
Use when any task touches git history, GitHub issues/PRs/releases/CI, repo governance, or branch and merge decisions. Runs the Fase Zero situational-awareness battery, picks one of five delivery flows via the adaptive decision engine, and enforces commit/PR information-density standards. Orchestrates the gh, git-workflows, github-actions, pr, and debug/finish skills.
adaptive-agenda-calendar-routine-engine
Use when planning or executing work across hours, days, weeks, or sprints. Turns the calendar into a strict time-blocked agenda (HH:MM-HH:MM blocks carrying a routine profile, expected inputs, and a handoff output artifact), runs the 5-stage cognitive flow (Radar and Hunt -> Triage plus Steve Jobs conception -> workbench manifest -> >=32-cycle loop -> Close plus Open-Minded Scrum), and unfolds macro calendar milestones into micro agenda blocks through extensions/gcal/wrapper.py.
demo
Use when demonstrating a skill in a fixture project.
duplicate-skill
Use when testing duplicate skill name detection.
duplicate-skill
Use when testing duplicate skill name detection.