fix-handoff-gate
Hand a fix to the independent verifier with a complete fix claim, honest status, deployed fingerprint, rollback plan, and a Done-Gate–compliant report, then react to the verdict. Use after the regression proof passes, and whenever reporting fix status to anyone.
71
89%
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
Handoff Gate
Procedure
- Fill
templates/fix-claim.json: bug IDs, branch, base, commit (= head), root cause, files, siblings fixed and listed, tests from the bug record, self-check evidence, deployed fingerprint, rollback, data repair, guard. - Status: PROPOSED or IMPLEMENTED, or FIXED IN DRAFT – DEPLOYED RETEST PENDING if not on the target. Never VERIFIED.
- Write the report in Done-Gate form: Not verified / Blocked / Not run / Not deployed first; every line names a bug ID and its exact status; numbers copied from the ledger; no hedged success.
- Run the claim auditor on the report; zero flags required.
- Send the claim to the verifier without your reasoning narrative.
- React: NOT FIXED → back to root cause; PARTIALLY FIXED → extend the sweep; regression → revert or flag off first, then rework. Record wrong attempts in the recipe library.
Exit criteria
The claim is delivered, the report passes the auditor, and any verifier rejection has a recorded next step.
Counterpart of tester skill: qa-release-gate.
- 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.