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.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
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
Verify provenance. "Deploy succeeded" means a job finished, not that the new build is being served.
/version.txt)noindex), and only the main branch deploys production<environment> <sha>)Report status: success / failed / rolled-back
Status: SUCCESS / FAILED / ROLLED_BACK Version: [version or commit hash] · Served SHA: [value from version endpoint] Duration: [time]
| Step | Status | Duration |
|---|---|---|
| Pre-flight | ✓ | 5s |
| Backup | ✓ | 2s |
| Deploy | ✓ | 10s |
| Health check | ✓ | 15s |
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Validates completed work against defined acceptance criteria. Use after completing a task that has specific success criteria defined in issues, specs, or task descriptions.
The English summary is being prepared. Showing the original description.
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. Use after happy-path tests exist and before claiming coverage is complete, when requirements lack tests, or before a security review.
The English summary is being prepared. Showing the original description.
Catches shortcuts and reward hacking — weakening or deleting tests to make them pass, hard-coding expected outputs, silently dropping requirements, or claiming work is done without running it. Use before declaring a task complete and whenever a test or requirement feels like it's in the way.
The English summary is being prepared. Showing the original description.
Safely integrates commits from parallel agent branches using sequential cherry-pick. Use after parallel work completes in isolated branches or worktrees.
The English summary is being prepared. Showing the original description.
Audits tests for concurrency safety — race conditions, shared mock state, cleanup ordering. Use when writing tests that involve goroutines, async operations, or shared mutable state.
The English summary is being prepared. Showing the original description.
Enforces tiered test coverage standards with three dimensions — line coverage by tier, spec-to-test traceability, and spec-to-code implementation mapping. Use before claiming code is complete.
The English summary is being prepared. Showing the original description.