agentleFS
ww-w-aiww-w-ai/bkit-gemini/skills/deploy/SKILL.md

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

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
  1. Very specific:

    Call bkit_checkpoint to create a restore point

    line 65
  2. Distinctive:

    All of dev checklist, plus:

    line 80
  3. Distinctive:

    All of staging checklist, plus:

    line 88
  4. Distinctive:

    After checklist is verified, provide the appropriate deploy command:

    line 99
  5. Distinctive:

    Verify the deployment was successful

    line 115
  6. Distinctive:

    Check health endpoints (if applicable)

    line 116
  7. Distinctive:

    Update PDCA status to "deployed"

    line 117
  8. Distinctive:

    Production requires explicit confirmation: - Never auto-deploy to prod

    line 141
  9. Distinctive:

    Checkpoint is mandatory: - Always create before deploy

    line 142
  10. Distinctive:

    Rollback ready: - Always provide rollback instructions with checkpoint ID

    line 144

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Deploy Skill

Guided deployment with pre-deploy checklist and checkpoint creation

Commands

CommandDescriptionExample
/deploy devDeploy to development/deploy dev
/deploy stagingDeploy to staging/deploy staging
/deploy prodDeploy 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:

  1. Call bkit_checkpoint to create a restore point
  2. Record the checkpoint ID for potential rollback
  3. 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 -c on 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 TODO or FIXME in 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:prod

4. Post-Deploy Verification

After deployment:

  1. Verify the deployment was successful
  2. Check health endpoints (if applicable)
  3. Update PDCA status to "deployed"
  4. 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 status

Safety Rules

  1. Production requires explicit confirmation - Never auto-deploy to prod
  2. Checkpoint is mandatory - Always create before deploy
  3. Match rate threshold - Warn if below required threshold for environment
  4. Rollback ready - Always provide rollback instructions with checkpoint ID

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.