deploy
Skill66 starsChanged 7 months agoApache-2.0View on GitHub
Deployment guidance and checklist for dev, staging, and production environments. Creates a checkpoint before deploy and provides a structured pre-deploy checklist.
155 other projects use a version of this.
Adopted by
Most recently taken up by
- pedrohcgs/claude-code-my-workflowtheir own version, first seen Nov 8, 2026
- KingKongRobotics/jumpertheir own version, first seen Nov 8, 2026
- stakeme-team/arc-agent-kittheir own version, first seen Nov 8, 2026
- dockhold/mcptheir own version, first seen Nov 8, 2026
- KhaiTrang1995/nexus-kbtheir own version, first seen Nov 8, 2026
- ribato22/vibechecktheir own version, first seen Nov 8, 2026
Other versions155 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 155
- ok-oldking/ok-wuthering-waves★ 8.6ksame name
- memovai/mimiclaw★ 5.8ksame name
- KingKongRobotics/jumper★ 3.1ksame name
- jhd3197/ServerKit★ 1.8ksame name
- pedrohcgs/claude-code-my-workflow★ 1.7ksame name
- mattmireles/gemma-tuner-multimodal★ 1.5ksame name
- microsoft/power-platform-skills★ 1.1ksame name
- jazzyalex/agent-sessions★ 941same name
- awslabs/agent-plugins★ 918same name
- patrickjaja/claude-desktop-extra★ 734same name
145 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 repository42 other files it gives its agents.
- auditSkill
- batchSkill
- bkend-authSkill
- bkend-cookbookSkill
- bkend-dataSkill
- bkend-guidesSkill
- bkend-mcpSkill
- bkend-quickstartSkill
- bkend-securitySkill
- bkend-storageSkill
- bkit-rulesSkill
- bkit-templatesSkill
- btwSkill
- code-reviewSkill
- controlSkill
- desktop-appSkill
- development-pipelineSkill
- dynamicSkill
- enterpriseSkill
- gemini-cli-learningSkill
- loopSkill
- mobile-appSkill
- output-style-setupSkill
- pdcaSkill
- phase-1-schemaSkill
- phase-2-conventionSkill
- phase-3-mockupSkill
- phase-4-apiSkill
- phase-5-design-systemSkill
- phase-6-ui-integrationSkill
- phase-7-seo-securitySkill
- phase-8-reviewSkill
- phase-9-deploymentSkill
- plan-plusSkill
- pm-discoverySkill
- qa-phaseSkill
- rollbackSkill
- simplifySkill
- skill-createSkill
- skill-statusSkill
- starterSkill
- zero-script-qaSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 9 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 139 edited versions we read keep these.
9
Distinctive
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 65
Call bkit_checkpoint to create a restore point
- Distinctive: line 80
All of dev checklist, plus:
- Distinctive: line 88
All of staging checklist, plus:
- Distinctive: line 99
After checklist is verified, provide the appropriate deploy command:
- Distinctive: line 115
Verify the deployment was successful
- Distinctive: line 116
Check health endpoints (if applicable)
- Distinctive: line 117
Update PDCA status to "deployed"
- Distinctive: line 141
Production requires explicit confirmation: - Never auto-deploy to prod
- Distinctive: line 142
Checkpoint is mandatory: - Always create before deploy
- Distinctive: line 144
Rollback ready: - Always provide rollback instructions with checkpoint ID
“Common” is measured: kept by at least 6 in 10 of the 139 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 Skill
Guided deployment with pre-deploy checklist and checkpoint creation
Commands
| Command | Description | Example |
/deploy dev | Deploy to development | /deploy dev |
/deploy staging | Deploy to staging | /deploy staging |
/deploy prod | Deploy to production (full checklist) | /deploy prod |
Note: Auto-deploy is not possible from the Gemini CLI Extension. This skill provides a guided checklist and ensures safety steps are taken. The actual deploy command must be run by the user or CI/CD pipeline.
How to Execute
1. Pre-Deploy Checkpoint
Before any deployment:
- Call
bkit_checkpointto create a restore point - Record the checkpoint ID for potential rollback
- Note: If checkpoint fails, warn user but do not block
2. Environment-Specific Checklists
Development (/deploy dev)
- All modified files saved
- No syntax errors (
node -con changed files) - Local tests pass (if configured)
- Checkpoint created
Staging (/deploy staging)
All of dev checklist, plus:
- PDCA Check phase completed (match rate >= 80%)
- No
TODOorFIXMEin changed files - Environment variables documented
- API changes backward-compatible
Production (/deploy prod)
All of staging checklist, plus:
- PDCA Check phase completed (match rate >= 90%)
- Code review completed (
/code-review) - All tests pass
- No debug/console.log statements
- Rollback plan documented
- PDCA report generated (
/pdca report) - Changelog updated
3. Deploy Command Guidance
After checklist is verified, provide the appropriate deploy command:
# Development
npm run deploy:dev # or project-specific command
# Staging
npm run deploy:staging
# Production
npm run deploy:prod4. Post-Deploy Verification
After deployment:
- Verify the deployment was successful
- Check health endpoints (if applicable)
- Update PDCA status to "deployed"
- Log the deployment in audit trail
Output Format
## Deploy Checklist: {environment}
### Pre-Deploy
- [x] Checkpoint created (ID: chk-20260409-143000)
- [x] Syntax check passed (12 files)
- [x] PDCA match rate: 94%
- [ ] Code review: PENDING
### Deploy Command
Run: `npm run deploy:staging`
### Post-Deploy
- [ ] Verify health endpoint
- [ ] Update PDCA statusSafety Rules
- Production requires explicit confirmation - Never auto-deploy to prod
- Checkpoint is mandatory - Always create before deploy
- Match rate threshold - Warn if below required threshold for environment
- Rollback ready - Always provide rollback instructions with checkpoint ID
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.

