to-commit

Commit ticket work as one Conventional Commit and tick verified acceptance criteria.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/dulltackle/kangkang-skills --skill to-commit-dulltackle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-commit
Source: https://github.com/dulltackle/kangkang-skills/tree/main/to-commit
Command: npx skills add https://github.com/dulltackle/kangkang-skills --skill to-commit-dulltackle

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about to-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I commit a finished ticket with verified acceptance criteria?

Run the to-commit skill at the end of a ticket session. It re-runs executable verifications, creates one Conventional Commit for the ticket, ticks only the criteria that passed, and asks you to confirm any criteria that were only code-reviewed.

How does the skill write back acceptance criteria to GitHub issues?

It re-reads the issue body with gh issue view, flips checkboxes only inside the acceptance-criteria region, writes the body back with gh issue edit, and appends a comment recording what was verified, unticked, or left for confirmation.

Does it work with local markdown ticket files instead of GitHub?

Yes. When docs/agents/issue-tracker.md configures a local markdown tracker, the ticket file is edited and committed together with the code, and closing an all-green ticket sets its Status line to done.

What happens when a pre-commit hook fails during the commit?

If the hook rewrote files, the skill re-stages and retries exactly once. If the hook refused, it stops and shows the hook output verbatim; --no-verify is never used, and on local trackers the ticket ticks are rolled back.

When does the skill push the branch and close the ticket?

Only when every acceptance criterion is ticked. It pushes first, then closes the ticket with a comment recording the commit and branch, so a failure never leaves a closed ticket whose code was never pushed.

What if the ticket has no acceptance criteria at all?

The skill commits the work normally but ticks nothing and never closes the ticket, since an empty criteria region can never go green. It states this plainly in the session output.