Skip to content

Skill

Conventional Commit

marcelorodrigo

Shapes the message of the commit you are about to make into the Conventional Commits format - a `type(scope): subject` header with an optional body, footer, and breaking-change marker that downstream tooling can parse. Its job is WORDING one commit; it does not rewrite past history, juggle branches, or assemble the release those commits eventually roll into.

Situations it fits

You made one small change and want its message to be concise and machine-readable so automation can classify it as a bug fix, new feature, or breaking change when building changelogs.
Conventional Commit. conventional-commit (marcelorodrigo) formats the single commit message so tooling can automatically detect its type (fix/feat/breaking) and include it in changelogs or CI checks; it’s specifically about wording the commit you’re about to make, not about rewriting past commits, opening a review, or tagging a release.
You finished a single small bugfix and are about to make one commit; the repo requires a rigid, machine-friendly commit header like "fix(api): ..." so CI and tooling can classify it. Write the message before you hit save.
Conventional Commit. conventional-commit shapes the wording of a single commit so it fits a predictable header-and-body pattern that automation can parse. The other skills operate on different levels: git-advanced-workflows rewrites or fixes history, create-pull-request publishes a branch for review, and release-skills handles tagging and shipping a release - none of those are about composing one commit message.
Your team enforces machine-readable commit messages so automated tooling can sort changes by category; you're about to make one commit and need help writing the message in the project's required format.
Conventional Commit. This skill formats a single commit message to meet a project's parseable convention so CI and release tools can classify it. It’s the right fit because the need is to word the commit you are about to make; the other skills operate on branches, repository surgery, or cutting releases, not composing one commit message.

5 scenarios in the bank answer to Conventional Commit. The rest are in the game.

Skills it gets confused with

These share a family with Conventional Commit, which is another way of saying they are the ones you might reach for by mistake.

Knowing what Conventional Commit does is the easy half. Telling it apart from the others under time pressure is the game.

Today's session

Conventional Commit is part of marcelorodrigo/agent-skills. Licence: MIT. The description above was written for this game, not taken from the skill.