deploy-service
Skill1 starsChanged 2 months agoMITView on GitHub
Take a change to production safely — pre-deploy checks, decouple schema/config/code steps, roll out gradually (flag / canary), watch the right signals, and know the rollback trigger before you start. Use when asked to "deploy", "ship this", "roll it out", or after a PR merges and needs to reach prod.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- NVIDIA/SkillSpectortheir own version, first seen Oct 13, 2026
- dream-horizon-org/pulsetheir own version, first seen Oct 8, 2026
- vefmvai/sysadmintheir own version, first seen Aug 19, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- NVIDIA/SkillSpector★ 25ksame name
- dream-horizon-org/pulse★ 44same name
- vefmvai/sysadmin★ 1same name
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 repository73 other files it gives its agents.
- AGENTS.mdAGENTS.md
- bigquery-analyticsSkill
- cache-invalidationSkill
- mongo-aggregationSkill
- mongo-modelingSkill
- postgres-aggregationSkill
- postgres-indexingSkill
- redis-coordinationSkill
- redis-patternsSkill
- review-querySkill
- code-migrationSkill
- cut-releaseSkill
- data-migrationSkill
- hotfixSkill
- rollbackSkill
- design-endpointSkill
- design-eventSkill
- design-schemaSkill
- evolve-contractSkill
- scaffold-nestjs-moduleSkill
- scaffold-projectSkill
- incident-responseSkill
- investigate-bugSkill
- on-callSkill
- postmortemSkill
- audit-skillsSkill
- distill-review-styleSkill
- write-skillSkill
- debug-with-tracesSkill
- define-alertsSkill
- instrument-serviceSkill
- evaluate-dependencySkill
- grillSkill
- handoffSkill
- orientSkill
- phased-deliverySkill
- spikeSkill
- to-questionnaireSkill
- write-adrSkill
- write-prdSkill
- devops-pr-reviewSkill
- go-backend-pr-reviewSkill
- nestjs-backend-pr-reviewSkill
- python-backend-pr-reviewSkill
- react-frontend-pr-reviewSkill
- bisectSkill
- break-couplingSkill
- dead-code-sweepSkill
- deslopifySkill
- extract-moduleSkill
- rebase-cleanSkill
- resolve-merge-conflictsSkill
- split-commitSkill
- tddSkill
- wait-whatSkill
- wide-renameSkill
- bullmqSkill
- kafkaSkill
- sqs-consumerSkill
- audit-dependenciesSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 37
If it's a release, tag it (deployment/cut-release).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Deploy a service
The devops pr-review skill reviews pipelines; this runs a rollout.
Before you start
- CI green — build, tests, lint, security-audit.
- The rollback plan is written and the trigger is defined ("if error rate > X for 5 min, roll back"). Know it before deploying, not during.
- Ordered steps if the change spans layers: schema migration first
(additive,
deployment/data-migration), then config, then code. New code must run against the old schema and vice versa. - Feature-flagged if the change is risky (
deployment/code-migration) — deploy dark, then ramp. - Anyone who needs to know is told (on-call, dependent teams for a contract change).
Rollout
- Prefer: canary / rolling / blue-green over the deploy target's mechanism, so a bad build doesn't hit 100% at once.
- Deploy → health check passes → small slice of traffic → watch → widen.
- Watch (
../observability/): error rate, p50/p99 latency, the metric the change was meant to move, saturation (pool / queue / CPU), downstream health. Watch for at least one full traffic cycle, not 30 seconds. - A
latestimage tag only moves for the default branch.
After
- Confirm the change actually does what it was for (not just "no errors").
- Close the loop: update the ticket, note anything surprising.
- If it's a release, tag it (
deployment/cut-release).
Anti-patterns
- ❌ Deploying without a written rollback trigger.
- ❌ Code and its schema migration in one indivisible step.
- ❌ 0 → 100% with no canary.
- ❌ "Looks fine" after 30 seconds.
- ❌ Deploying on a Friday afternoon / before being AFK, for anything non-trivial.
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.