skills.rest
LadderChaos
LadderChaosCOMMUNITY
Explore all skills by this author →
GitHub

conventional-commits

Validate commit messages against the conventional commits format.

Updated Aug 27, 2026
Search Tags:#git#changelog#pre-commit#semantic-versioning#conventional-commits#commit-messages
One-click install
npx skills add https://github.com/LadderChaos/tora-skills --skill conventional-commits-ladderchaos
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: conventional-commits
Source: https://github.com/LadderChaos/tora-skills/tree/main/conventional-commits
Command: npx skills add https://github.com/LadderChaos/tora-skills --skill conventional-commits-ladderchaos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conventional commits standardize commit messages across a repository, improving readability and enabling automated changelogs.

Core Features & Use Cases

  • Enforces the conventional commits format for new commits
  • Generates changelogs and release notes from commit messages
  • Validates commit messages in pre-commit hooks or CI to catch formatting issues

Quick Start

Use this skill when crafting commit messages to follow the format: <type>(<scope>): <subject>. For example, feat(auth): add OAuth2 login.

Frequently Asked Questions about conventional-commits

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce conventional commit messages in git?▼

A conventional commit message follows the format <type>(<scope>): <subject>, such as feat(auth): add OAuth2 login, with optional sections for breaking changes, body, and footer to standardize repository history.

How do I generate a changelog from commit messages?▼

You can generate changelogs and release notes from commit messages by enforcing the conventional commits format, which enables automated tools to parse commit types and scopes to produce readable release documentation.

Can I validate commit message formatting in pre-commit hooks?▼

Yes, you can validate commit messages in pre-commit hooks to catch formatting issues, checking that the type, scope, and subject conform to conventional commit standards before allowing a commit to proceed.

Does conventional commits support breaking changes in the commit body?▼

Conventional commits standardize commit messages across a repository to improve readability and enable automated changelogs, whereas other software engineering approaches may lack strict type and scope validation for history generation.

Related Skills

Explore More Software Engineering Skills→
HyperxqHyperxq
1

lefthook

Enforce Conventional Commits and run Git hooks via Lefthook.

Community
Intermediate
sgcarstrendssgcarstrends
21

changelog

Generate CHANGELOG.md from conventional commits using semantic-release.

Official
Advanced
kreuzberg-devkreuzberg-dev
836

git-standards

Enforce Conventional Commits and pre-commit hooks for formatting, linting, and tests.

Official
Intermediate
axone-protocolaxone-protocol
124

conventional-commits

Enforce Conventional Commits structure for commit messages.

Official
Intermediate