commit

Enforce Conventional Commits format for git commit messages.

562|80|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/kdlbs/kandev --skill commit-kdlbs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/kdlbs/kandev/tree/main/.agents/skills/commit
Command: npx skills add https://github.com/kdlbs/kandev --skill commit-kdlbs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conventional git commit messages are critical for meaningful changelogs and release notes, but teams often forget or diverge from the standard, leading to noisy history and broken automation.

Core Features & Use Cases

  • Enforces Conventional Commits formatting: type, optional scope, and description.
  • Guides users with allowed types and example messages to keep history clean.
  • Use cases include preparing commits for main/PRs, generating changelogs via CI tooling, and ensuring consistent release notes.

Quick Start

Create a conventional commit message describing your change and commit it.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate git commit messages to follow conventional commits?

Automate git commit messages by enforcing the Conventional Commits specification with a required type, optional scope, and description format. This ensures consistent history and clean changelogs during development workflows.

What is the conventional commits format for type and description?

The conventional commits format requires a type, an optional scope, and a description, structured as type: description. Supported types are provided with example messages to guide users in keeping git history clean.

Can I use conventional commit messages for squash merges and CI validation?

Yes, conventional commit messages can be applied during squash merges and CI validation. Enforcing this standard during development workflows ensures meaningful changelogs and reliable release notes generation.

Why do my automated changelogs and release notes have noisy git history?

Noisy git history and broken automation often occur because teams forget or diverge from the conventional commits standard. Enforcing consistent commit message formatting with required types solves this problem for changelog generation.

What are the allowed types when preparing conventional commits for pull requests?

Allowed types for conventional commits are provided within the guidelines to help structure pull request commits correctly. Using these supported types with an optional scope ensures PR history remains clean and automation-friendly.