conventional-commitslisted

The Conventional Commits format — also called "semantic commits" / semantic commit messages — a `type(scope): description` header (`feat`, `fix`, …) plus an optional `BREAKING CHANGE` footer, and how it makes history machine-readable to drive automated version bumps and changelogs. Use when writing a commit message or PR title, deciding the type/scope/bump for a change, setting up or fixing a repo's commit convention, making commits parseable by semantic-release / changelog tooling, validating PR titles, or when a release didn't bump or the changelog came out blank because a commit wasn't conventional. Covers the type→semver mapping, breaking changes, scopes, monorepo scopes, and squash-merge PR titles.
stealth-engine/skills · ★ 2 · Code & Development · score 76

Install: claude install-skill stealth-engine/skills

# Conventional Commits (a.k.a. semantic commit messages) A commit convention that makes history **machine-readable**: a parser reads each message, decides the next semver version, and builds the changelog from it. "Semantic commits" is the common nickname for the same thing. It's the foundation the release automation stands on — [`semantic-release-automation`](../semantic-release-automation/SKILL.md) covers the tooling that consumes these messages. ## The format ```text <type>[(<scope>)][!]: <description> <optional body — the "why", wrapped> <optional footer(s) — BREAKING CHANGE:, Closes #123, Refs: ABC-12> ``` - `type` / `scope`: lowercase **by convention** — the spec is case-*insensitive*, except `BREAKING CHANGE`, which MUST be uppercase. `scope` is an optional noun in parens for the area touched. - `!` before the colon **or** a `BREAKING CHANGE:` footer marks a breaking change (`BREAKING-CHANGE:` with a hyphen is an accepted synonym). - **description**: concise; **by convention** imperative mood, lowercase, **no trailing period** (Angular/commitlint style — the spec itself mandates none of these). - Blank line before any body/footer. ```text feat(auth): add passkey sign-in fix(parser): handle empty input without throwing feat(api)!: drop the v1 token endpoint docs: fix typo in install steps ``` ## Types → meaning → version bump These are the **semantic-release defaults** (the `angular` preset plus commit-analyzer's built-in release rules). They're confi