Conventional Commits

Format all commit messages per the Conventional Commits v1.0.0 spec. Use when creating commits, reviewing commit messages, or discussing git workflow. Use when this capability is needed.

tomevault-io Updated

File contents

Conventional Commits

Spec: https://www.conventionalcommits.org/en/v1.0.0/

Format

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Types

  • feat — new feature (SemVer MINOR)
  • fix — bug fix (SemVer PATCH)
  • Also permitted: build, chore, ci, docs, style, refactor, perf, test

Rules

  • Scope is optional, in parentheses: feat(parser):
  • Description MUST immediately follow the colon and space
  • Body is optional, separated by one blank line from description
  • Footers are optional, separated by one blank line from body
  • Breaking changes: add ! before colon OR use BREAKING CHANGE: footer (SemVer MAJOR)
  • BREAKING CHANGE MUST be uppercase
  • Footer tokens use hyphens for spaces (e.g., Acked-by)

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

tomevault-io/skills-registry/tree/main/simpleapps-com--augur-skills--conventional-commits commit c62657bc5f

Frequently asked questions

npx skillmds@latest add tomevault-io/conventional-commits-6