conventional-commits

Generate commit messages following the Conventional Commits specification.

2|Updated Nov 12, 2025
One-click install
npx skills add https://github.com/stlwolf/ai-development-hub --skill conventional-commits-stlwolf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conventional-commits
Source: https://github.com/stlwolf/ai-development-hub/tree/main/canonical/skills/conventional-commits
Command: npx skills add https://github.com/stlwolf/ai-development-hub --skill conventional-commits-stlwolf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating commit messages that follow the Conventional Commits specification, which helps standardize commit history across projects and simplifies release notes.

Core Features & Use Cases

  • Enforces Conventional Commits types (feat, fix, docs, chore, etc.) and formatting for subject lines.
  • Supports scope, body, and footer conventions to capture context and breaking changes.
  • Use Case: streamline collaboration in multi-repo teams by ensuring consistent, machine-readable commit messages that feed release notes and versioning.

Quick Start

Describe your change, and the tool will generate a standardized Conventional Commits message.

Frequently Asked Questions about conventional-commits

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

FAQPage Schema
How do I generate conventional commit messages automatically?

You can generate conventional commit messages automatically by describing your code change to the tool, which then formats it with correct prefixes like feat, fix, and docs to standardize your git history.

What is the conventional commits format and when do I need it for git?

The conventional commits format standardizes git commit history by enforcing structured prefixes like feat and fix, which is needed when you want to automate release notes and semantic versioning across multi-repo teams.

How do I format commit scopes, bodies, and breaking changes?

To format commit scopes, bodies, and breaking changes, the tool applies conventional commits conventions, capturing context in the scope and body while appending specific footers to indicate breaking changes.

Does this conventional commits tool support custom commit types beyond feat and fix?

The tool enforces standard conventional commits types including feat, fix, docs, and chore, ensuring consistent subject line formatting for software development workflows without requiring custom type configurations.

Can I use conventional commits to streamline release notes for multi-repo teams?

Yes, you can use conventional commits to streamline collaboration in multi-repo teams by generating machine-readable commit messages that directly feed into automated release notes and versioning.