Skills · Code

CodeSkillDugout-created

/commit-messages

Writes commit messages and branch names that say what is now true, scoped to the ticket or the area of the code.

Created by Piyush Baheti · Source: piyush-tkd/skillsdugout/tree/main/plugins/commit-messages

Who it is for

Developers who want a git log people can read and trace back to tickets.

When to use it

  • A change is ready to commit.
  • You are naming a new branch.
  • Your log is full of "fix stuff" and missing ticket numbers.

Example

You ask

Write the commit message and branch name. Ticket SHOP-212. Discount codes were compared case-sensitively in cart/discount.ts; now both sides are lowercased. Customers typing "save10" instead of "SAVE10" were told the code was invalid — 37 support complaints last month.

Without the skill

Branch: fix/SHOP-212-case-insensitive-discount-codes

fix(cart): compare discount codes case-insensitively

Discount code validation in cart/discount.ts compared the entered code
to the stored code case-sensitively, so customers typing "save10"
instead of "SAVE10" were told the code was invalid. Support logged 37
of these complaints last month.

Lowercase both sides before comparing. Stored codes keep their original
casing; only the comparison is normalized.

Refs: SHOP-212

With /commit-messages

fix(SHOP-212): discount codes match regardless of case

Customers typing "save10" instead of "SAVE10" were told the code was
invalid. Support logged 37 of those complaints last month. Both sides
are now lowercased in cart/discount.ts before comparing.

Branch: fix/SHOP-212/discount-codes-match-regardless-of-case

Sample runs on 2026-10-03: the same request to the same model, with and without the skill. Co-author trailers removed from the run without the skill.

Evidence

Our test

No baseline test yet. We will publish one, with and without the skill, when testing is done.

Reported by the community, by app

Claude Code: Tested
No outcomes reported yet
Claude apps: Not tested
No outcomes reported yet
Cursor: Not tested
No outcomes reported yet
Codex: Not tested
No outcomes reported yet
GitHub Copilot: Not tested
No outcomes reported yet

Compatibility labels come from our tests only. Community reports add detail but cannot mark an app as tested.

Editorial assessment · not a community rating

Editorial review in progress

We have not finished testing this listing against doing the task without it. The verdict appears here when we have. Our team made this skill; it gets the same test as external work.

How we review

Setup and customization

  • Works with no setup after install.
  • If your repository documents its own commit rules, those win.

What it can access

Reads
The conversation; The staged change, if you ask it to look
Changes
Nothing; you run the commit

Install

Claude Code: Tested
  1. Add the Skills Dugout marketplace once.
    /plugin marketplace add piyush-tkd/skillsdugout
  2. Install /commit-messages.
    /plugin install commit-messages@skillsdugout
  3. Start a new session and ask for it, for example "write the commit message".

Community reviews

No reviews yet. Be the first to rate it after you try it.

Each review records the app, version, task and outcome; those outcomes feed the Evidence section. One rating per person; creators reply but cannot rate their own work.

No reviews yet. Be the first to rate it after you try it.

Source, license and versions

Source
github.com/piyush-tkd/skillsdugout/tree/main/plugins/commit-messages
License
MIT, as stated in the repository
  • 0.1.0 · 2026-10-03 · First release.
Show the full skill instructions

Writing a commit message

Overview

Based on Conventional Commits v1.0.0: type(scope): description.

Two house conventions go beyond the spec, which makes the scope optional and says nothing about branches:

  • The scope is required. It is one of exactly two things — the ticket, or the area of the codebase.
  • Branches take the same three parts: type/scope/description-in-kebab-case.

The description says what is now true, not what was done.

If the repository documents its own commit convention, that convention wins. Use this skill for whatever it leaves open.

The ticket

  • Use the ticket already given for the task, if there is one.
  • If the repository requires a ticket and none was given, ask once.
  • Otherwise use an area scope.
  • Never infer a ticket from the branch, the diff, or a nearby commit, and never invent one.
Situation Commit Branch
Ticket ABC-400 given feat(ABC-400): invoices retry on timeout feat/ABC-400/invoice-retry-on-timeout
No ticket feat(checkout): tax comes from the address feat/checkout/tax-from-address

A formatting-only change is still style(scope):, with no body.

Quick reference

Element Rule
Type feat fix docs style refactor perf test build ci chore revert
Ticket scope The tracker key, uppercase, with its number: ABC-400
Area scope Lowercase kebab: checkout auth devops nav
Scope Never empty. Never both a ticket and an area
Description Lowercase, present tense, the new state, ≤ 100 chars
Breaking ! before the colon, plus a BREAKING CHANGE: footer when the migration needs explaining
Body Optional. Only when it carries content — see below
Trailers None by default, including AI co-author trailers. Add one only when the user or repo asks for it

Common mistakes

Mistake Instead
Fix search combining filters with OR fix(ABC-481): search requires all selected filters
ABC-33: wire retry scheduler chore(ABC-33): retry scheduler backs off
DEVOPS: derived checks chore(devops): derived checks for the conventions
feat: add saved cards feat(checkout): saved cards appear at checkout
feat(ABC-NNN): … Use the given ticket, or an area scope
Branch ABC-372-qa fix/ABC-372/qa-config

Red flags — stop

  • No type, or a type with an empty scope
  • A bare ABC-400: or DEVOPS: with no type
  • NNN, XXX, or a ticket key nobody gave you
  • A description opening with a capital or an imperative verb ("add", "fix", "update")
  • A trailer nobody asked for
  • A branch missing its type segment, or with the ticket glued on by a dash

Passing commitlint is not evidence. Check what the repo's config actually enforces before treating a pass as proof of anything.


Reference

Choosing the scope

Situation Scope Example
A ticket exists The key, uppercase, with its number fix(ABC-446): document types reconcile
No ticket The area, lowercase kebab-case chore(devops): derived checks for the conventions

The branch name is not evidence — branches get reused. A log full of ABC-NNN: placeholders or misspelt keys is what filling the slot instead of checking produces.

Prefer an area scope that already exists in git log. docs is both a type and an area: when documentation changes, the type carries it and the scope names the subject — docs(billing): …, not docs(docs): ….

Types

feat a new capability; fix a bug fix; docs documentation only (incl. CLAUDE.md); style formatting, no behaviour change; refactor same behaviour, different shape; perf a measured speed or memory change; test tests only; build build tool, dependencies, Dockerfile, packaging; ci pipelines, hooks, CI scripts; chore anything else with no product effect; revert undoing a commit, naming it in the body.

Breaking changes

feat(ABC-400)!: order payload drops the type column

BREAKING CHANGE: order.type is gone. Clients read attributes instead.

Always use the ! — it is what a reader scanning git log --oneline sees. Add the footer when the migration needs explaining. BREAKING-CHANGE is a synonym; the token must be uppercase.

The body, when there is one

Up to four parts, in this order. Each is optional; include only the ones that add something, and never invent one.

  1. Why — the problem this solves. A number helps when there is a real one.
  2. What was rejected — the obvious alternative, if a reader would otherwise ask why not.
  3. What it costs — who or what is affected.
  4. What is still not fixed — a known limitation, stated rather than hidden.

Correcting yourself

Open plainly and do not bury it — for example "Corrects the previous commit, which claimed X was unused by every caller. It is not." That habit is what makes the rest of the log trustworthy.

Branch naming

type/scope/description-in-kebab-case, the same three parts as the commit: feat/ABC-400/invoice-retry-on-timeout, chore/devops/repo-guardrails. If a branch-name hook exists, check its pattern accepts both ticket and area scopes before relying on it.

Smart Commits (Jira) — optional

Only when the repo is linked to Jira and the user has asked for it. Smart Commits change the ticket: #comment posts a comment, #time 2h logs work, and transition commands such as #resolve move the ticket through its workflow, depending on how that workflow is configured. They are actions, not formatting — never add one by default.