Menu
Performs deployment with pre-flight checks, atomic replacement, post-deploy verification, and automatic rollback. Use before any deployment to staging or production.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | vibe-safe-deploy |
| description | Performs deployment with pre-flight checks, atomic replacement, post-deploy verification, and automatic rollback. Use before any deployment to staging or production. |
| user-invocable | true |
Ship with confidence. Every deployment should be verifiable and reversible.
Before deploying, verify:
grep -r 'API_KEY\|SECRET\|PASSWORD')Pre-flight checks — Run all items in checklist. Stop if any fail.
Backup current state:
cp -r current_deploy/ current_deploy.prev/
# or: docker tag app:current app:rollback
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
Health check (within 60s timeout):
If health check fails → automatic rollback:
cp -r current_deploy.prev/ current_deploy/
# Restart services with previous version
Report status: success / failed / rolled-back
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 |
Dispatches research agents to find real projects, papers, and documented failures before proposing any feature, architecture, or technology choice. Triggers on creative/design tasks, not on implementation of already-designed specs.
Validates completed work against defined acceptance criteria. Use after completing a task that has specific success criteria defined in issues, specs, or task descriptions.
Generates edge case, failure mode, and spec-driven test cases. Covers boundary values, nil inputs, concurrency, resource exhaustion, malformed data, and requirement-linked traceability tests.
Detects and prevents shortcut rationalization — when the agent is about to skip a step, simplify a requirement, or optimize away a constraint. Triggers proactively when rationalization patterns are noticed.
Provides a persistent cross-session task queue for work that should be done but isn't blocking current tasks. Enables background and future-session work tracking.
Safely integrates commits from parallel agent branches using sequential cherry-pick. Use after parallel work completes in isolated branches or worktrees.