Release pipeline
Complete release pipeline across three phases: (1) Completing & Releasing — verify tests, merge/PR, automated changelog + version bump + tag + GitHub Release, /ship and /land-and-deploy; (2) Deployment Strategies — Docker multi-stage builds, CI/CD pipelines, rolling/blue-green/canary patterns, health checks, rollback; (3) Canary Watch — post-deploy HTTP monitoring, error rate detection, SSE streams, static asset checks. Incorporates: completing-and-releasing, deployment-strategies, canary-watch.From its SKILL.md
npx -y skills add asong56/skills --skill release-pipelineAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.4 KB, 199 tokens by cl100k_base, as published. Nobody here has run it
Release Pipeline — Dispatch
Three sequential phases of a production release. Load the relevant reference file.
| Phase | File | Use when |
|---|---|---|
| Completing & Releasing | references/completing-releasing.md | Finishing a branch: tests → merge/PR → changelog → tag → GitHub Release → /ship → /land-and-deploy |
| Deployment Strategies | references/deployment-strategies.md | Choosing and executing a deploy strategy (rolling, blue-green, canary, Docker, K8s) |
| Canary Watch | references/canary-watch.md | Post-deploy monitoring: HTTP status, error rates, performance regressions |
Typical flow
1. /complete → loads completing-releasing.md
2. /deploy → loads deployment-strategies.md
3. /canary → loads canary-watch.md
Load the phase file before executing any release commands.
What ships with it: 3 files
134.6 KB alongside SKILL.md
references/
- canary-watch.md2.7 KB
- completing-releasing.md100.7 KB
- deployment-strategies.md31.2 KB