// Conventional Commits specification for consistent, machine-readable git commit messages. Use when crafting commit messages, enforcing commitlint rules, or generating changelogs/releases.
| name | conventional-commits |
| description | Conventional Commits specification for consistent, machine-readable git commit messages. Use when crafting commit messages, enforcing commitlint rules, or generating changelogs/releases. |
| metadata | {"author":"Conventional Commits community","version":"2026.03.01","source":"https://github.com/conventional-commits/conventionalcommits.org"} |
A lightweight convention for commit messages that enables automated tooling (changelogs, releases) and improves human readability.
<type>[optional scope][!]: <description>
[optional body]
[optional footer(s)]
auth, ui, deps.BREAKING CHANGE: or issue references.Common types used by popular tooling (commitlint, semantic-release):
Indicate breaking changes with ! or a footer:
feat(api)!: remove deprecated endpoints
BREAKING CHANGE: `/v1/users` no longer accepts `status`.
feat(chat): add streaming response support
fix(ui): handle empty history state
refactor(store): simplify session persistence
chore(deps): bump vue to 3.5.6
Refs: #123 or Closes #123.Anthony Fu's opinionated tooling and conventions for JavaScript/TypeScript projects. Use when setting up new projects, configuring ESLint/Prettier alternatives, monorepos, library publishing, or when the user mentions Anthony Fu's preferences.
Node.js package manager with strict dependency resolution. Use when running pnpm specific commands, configuring workspaces, or managing dependencies with catalogs, patches, or overrides.