Skip to content

ash1794/vibe-engineering / plugins/vibe-engineering/skills/vibe-safe-deploy

vibe-safe-deploy

Verified

Performs deployment with pre-flight checks, atomic replacement, post-deploy verification, provenance (proving the environment serves the exact commit you pushed), and automatic rollback. Use before any deployment to staging, preview, or production.

vibe-safe-deploy

Ship with confidence. Every deployment should be verifiable and reversible.

When to Use This Skill

  • Deploying to staging or production environments
  • Releasing a new version
  • Deploying infrastructure changes

When NOT to Use This Skill

  • Local development builds
  • CI/CD that already handles these checks
  • Deploying documentation (low risk)

Pre-Flight Checklist

Before deploying, verify:

  • All tests pass (including integration tests)
  • Linting is clean
  • No uncommitted changes in working tree
  • No secrets in the diff (grep -r 'API_KEY\|SECRET\|PASSWORD')
  • Build succeeds
  • Database migrations are reversible (if applicable)

Steps

  1. Pre-flight checks — Run all items in checklist. Stop if any fail.

  2. Backup current state:

    cp -r current_deploy/ current_deploy.prev/
    # or: docker tag app:current app:rollback
    
  3. Deploy using atomic operations:

    # Use 'install' not 'cp' for atomic file replacement
    install -m 755 new_binary /path/to/binary
    # or: docker tag app:new app:current && docker-compose up -d
    
  4. Health check (within 60s timeout):

    • Service starts successfully
    • Health endpoint returns 200
    • Key functionality works (smoke test)
    • No error spikes in logs
  5. If health check fails → automatic rollback:

    cp -r current_deploy.prev/ current_deploy/
    # Restart services with previous version
    
  6. Verify provenance. "Deploy succeeded" means a job finished, not that the new build is being served.

    • Bake the commit SHA into the build or image and serve it at a version endpoint (for example /version.txt)
    • After deploy, poll that endpoint until it returns the expected SHA; on timeout, fail and report the SHA it actually served
    • Keep environments separate: branch pushes deploy preview (behind auth, noindex), and only the main branch deploys production
    • Give the deploy credential the least privilege that works (for example a forced-command SSH key that accepts only <environment> <sha>)
  7. Report status: success / failed / rolled-back

Output Format

Deployment Report

Status: SUCCESS / FAILED / ROLLED_BACK Version: [version or commit hash] · Served SHA: [value from version endpoint] Duration: [time]

StepStatusDuration
Pre-flight✓5s
Backup✓2s
Deploy✓10s
Health check✓15s

Post-Deploy Verification

  • Service running: ✓
  • Health endpoint: 200 OK
  • Log errors: 0 in last 60s
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 319kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall