fix-deploy-rollback
Get a fix onto the build the verifier will test, with matching fingerprints, production config, migrations applied safely, and a rehearsed rollback; never deploy to production without approval. Use when a fix needs deploying for verification or release.
72
90%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Deploy and Rollback
Procedure
- The claimed commit must be the branch head. Never claim an older commit while the head contains other changes.
- Deploy to the verification target (staging) within scope; record the deployed fingerprint and confirm it matches the head.
- Run with production config values; a fix that only works outside production isn't a fix.
- Migrations: apply on a copy first, check counts and checksums, have a down-migration or restore.
- Rollback: rehearse reverting to the previous build in staging and confirm the app works and new data stays readable.
- Read effective config inside the running service after deploy.
- Production promotion is a separate human approval.
Exit criteria
Deployed fingerprint = branch head = claimed commit, rollback rehearsed (or BLOCKED with the risk named), production untouched without approval.
Counterpart of tester skill: qa-deploy-migration-rollback.
- Repository
itsablabla/qa-bug-agent-skills
- Revision
9a6f628
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.