Vibe Safe Deploy
Performs deployment with pre-flight checks, atomic replacement, post-deploy verification, and automatic rollback. Use before any deployment to staging or production.
Install
$ agentstack add skill-ash1794-vibe-engineering-safe-deploy ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
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
- Pre-flight checks — Run all items in checklist. Stop if any fail.
- Backup current state:
``bash cp -r current_deploy/ current_deploy.prev/ # or: docker tag app:current app:rollback ``
- Deploy using atomic operations:
``bash # 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 ``
- Health check (within 60s timeout):
- Service starts successfully
- Health endpoint returns 200
- Key functionality works (smoke test)
- No error spikes in logs
- If health check fails → automatic rollback:
``bash cp -r current_deploy.prev/ current_deploy/ # Restart services with previous version ``
- Report status: success / failed / rolled-back
Output Format
Deployment Report
Status: SUCCESS / FAILED / ROLLED_BACK Version: [version or commit hash] Duration: [time]
| Step | Status | Duration | |------|--------|----------| | 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
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ash1794
- Source: ash1794/vibe-engineering
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.