commit-message-convention-guide

Drafts, reviews, and repairs commit messages written in the Conventional Commits format, and helps a team adopt it. Covers picking a type (including custom types a project has configured) and a scope, wording the subject and body, marking breaking changes, revert messages, correcting unpushed commits locally, and rollout options such as lint hooks and squash merges. Use when asked how to word or format a commit message, whether a change counts as a feat, a fix, or a project-defined type, how to flag a break, how to reword a commit that has not been pushed, or how to introduce the convention across contributors. Not for running releases, changelog or version-bump automation, or rewriting commits that already exist on a remote.

Version

v1.0.0

Size

18 KB

Updated

2026-10-12

Your client verifies the signature before reading. This explicit manual read is available on every plan. Free automatically loads five chosen skills; paid plans automatically load relevant skills across the library.