deployment-procedures
Skill2 starsChanged 6 months agoMITView on GitHub
Production deployment procedures with rollback plans, health checks, and verification steps. Use when deploying to production, planning rollback strategies, or verifying production health after deployment.
15 other projects use a version of this.
Adopted by
Most recently taken up by
- AtilaMedeiros/skillstheir own version, first seen Nov 16, 2026
- Ivan-propio/claude-skillstheir own version, first seen Nov 16, 2026
- rajdeepbhattacharyya25-pixel/agents-for-antigravity-their own version, first seen Nov 15, 2026
- sid-lakhani/agents-configtheir own version, first seen Oct 20, 2026
- xfstudio/skillstheir own version, first seen Oct 13, 2026
- xenitV1/Antigravity-Workflowstheir own version, first seen Oct 8, 2026
Used with
Projects with it also use intelligent-routing, nextjs-react-expert and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
SKB3002Skillintelligent-routing
Automatic agent selection and intelligent task routing. Analyzes user requests and automatically selects the best specialist agent(s) without requiring explicit user mentions.
Also in 6 projects that use this
SKB3002Skillnextjs-react-expert
React and Next.js performance optimization from Vercel Engineering. Use when building React components, optimizing performance, eliminating waterfalls, reducing bundle size, reviewing code for performance issues, or implementing server/client-side optimizations.
Also in 3 projects that use this
xfstudioSkillrust-pro
Master Rust 1.75+ with modern async patterns, advanced type system
Also in 5 projects that use this
goca-seSkillbatch-operations
Apply a change safely across many files — refactors touching more than 5 files, library or API migrations, project-wide renames of symbols/imports/paths, or adding boilerplate to many files. Use when "do it all at once" risks context overflow or silent failures.
Also in 3 projects that use this
jornalistainclusivoSkilldesign-spec
How to author a DESIGN.md file — the machine-readable design-token + human-rationale format that must exist before any UI is built. YAML front-matter token schema (colors, typography, spacing, rounded, components), type system, token references, and canonical section order.
Also in 3 projects that use this
sefaertuncSkillcoordinator-mode
Multi-agent orchestration patterns: when to use coordinator mode, worker prompts, parallel execution
Also in 3 projects that use this
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 15
- vudovn/ag-kit★ 8.2ksame name
- vudovn/antigravity-kit★ 8.2ksame name
- xenitV1/Antigravity-Workflows★ 130same name
- VoDaiLocz/kilo-kit-mcp★ 27same name
- soumatheusgomes/agentville★ 9same name
- xfstudio/skills★ 9same name
- SKB3002/agenthub★ 4same name
- ai4brands-design/claude-skills★ 2same name
- sid-lakhani/agents-config★ 2same name
- AtilaMedeiros/skills★ 1same name
5 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository40 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ai-skillsSkill
- analyze-localSkill
- analyze-prodSkill
- analyzeSkill
- architectureSkill
- asset-validationSkill
- blog-postSkill
- bugfixSkill
- cloud-platformsSkill
- code-reviewSkill
- content-creationSkill
- context-engineeringSkill
- create-prSkill
- deploy-productionSkill
- deploy-stagingSkill
- docsSkill
- feature-devSkill
- geo-writerSkill
- humanizerSkill
- infra-changeSkill
- marketing-operationsSkill
- marketingSkill
- ml-pipelineSkill
- planSkill
- pre-commitSkill
- productSkill
- project-initSkill
- prompt-engineeringSkill
- qaSkill
- releaseSkill
- run-testsSkill
- security-scanSkill
- seo-reviewSkill
- social-media-managerSkill
- test-localSkill
- test-strategySkill
- ui-ux-designSkill
- worktree-isolationSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 47
If healthy → gradually increase traffic (25% → 50% → 100%)
- Distinctive: line 48
If degraded → route all traffic back to stable version
- Distinctive: line 53
Run full smoke tests against green
- Distinctive: line 55
Keep blue running for instant rollback (15–30 minutes)
“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Deploy to Production
Production deployment skill providing rollback procedures, health check patterns, and verification checklists. Ensures safe, repeatable production deployments.
When to Use
- Deploying application updates to production
- Planning rollback strategies before deployment
- Verifying production health after deployment
- Investigating post-deployment issues
When NOT to Use
- Deploying to staging (use
deploy-stagingskill workflow) - Making infrastructure changes (use
infra-changeskill workflow) - Planning release version and changelog (use
releaseskill workflow)
Deployment Strategies
| Strategy | When to Use | Risk | Downtime |
| Rolling update | Standard deploys, stateless services | Low | Zero |
| Blue-Green | Critical services, instant rollback needed | Low | Zero |
| Canary | High-risk changes, gradual validation | Medium | Zero |
| Recreate | Stateful services, breaking schema changes | High | Brief |
Rolling Update (Default)
- Gradually replace old pods with new ones
- Health checks gate the rollout — unhealthy pods stop the rollout
- Configure
maxSurgeandmaxUnavailablefor rollout speed - Monitor error rates during rollout window
Canary Deployment
- Deploy new version to small subset (5–10% traffic)
- Monitor error rate, latency, and business metrics for 5–10 minutes
- If healthy → gradually increase traffic (25% → 50% → 100%)
- If degraded → route all traffic back to stable version
Blue-Green Deployment
- Deploy new version alongside current (green alongside blue)
- Run full smoke tests against green
- Switch traffic from blue to green
- Keep blue running for instant rollback (15–30 minutes)
- Decommission blue after confidence period
Pre-Deployment Checklist
- All tests pass on release branch
- Staging deployment verified
- Database migrations tested (forward and rollback)
- Feature flags configured
- Monitoring dashboards ready
- On-call team notified
- Rollback plan documented and tested
- Release notes prepared
Post-Deployment Verification
- Health endpoint returns 200
- Error rate ≤ pre-deploy baseline
- Latency P95 within SLO target
- No new error patterns in logs
- Key user journeys functional
- Database connections stable
- External integrations responding
- Alerts not firing
Integration
- Follows rules:
devops-engineerrole (infrastructure),sre-engineerrole (SLOs, monitoring) - Used by workflows:
deploy-productionskill,deploy-stagingskill - Companion resources:
rollback-procedure.md
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

