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.

A situation 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 (marcelorodrigo). 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.

5 scenarios in the bank answer to conventional-commit (marcelorodrigo). The rest are in the game.

Skills it gets confused with

These share a family with conventional-commit (marcelorodrigo), which is another way of saying they are the ones you might reach for by mistake.

Knowing what conventional-commit (marcelorodrigo) does is the easy half. Telling it apart from the others under time pressure is the game.

Today's session

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

← All skills