What problem does it solve? Finishing a coding ticket often ends with a messy commit, forgotten acceptance criteria, and a ticket closed on trust rather than evidence. This Skill enforces a disciplined end-of-ticket workflow: one commit per ticket, every acceptance criterion verified before it is ticked, and the ticket closed only when all criteria are earned. ## Core Features & Use Cases - Evidence-based criteria ticking: Each acceptance criterion is classified as verified-by-execution or read-only; only executed criteria get ticked automatically, while read-only ones require explicit user confirmation. - Tracker-aware write-back: Supports GitHub (via gh CLI), other remote trackers, and local markdown ticket files, with the commit/write-back order flipped per tracker to keep both in sync. - Safe failure handling: Pre-commit hook failures, push refusals, and write-back mismatches stop the run with honest split-state reports instead of forced retries or --no-verify workarounds. - Use Case: After an /implement session finishes a feature ticket, run this Skill to re-run the tests, commit everything as one Conventional Commit, tick the verified criteria on issue #42, ask you about the two criteria that were only code-reviewed, then push the branch and close the ticket. ## Quick Start Ask the AI to commit the current ticket session with the to-commit skill, verifying each acceptance criterion before ticking it and closing the ticket only when all are earned.