conventional-commit

Name: conventional-commit
Availability: InStock
Author: Kota

Enforce Conventional Commits spec for commit messages across repositories and teams.

1|Updated Jan 20, 2026

Search Tags:#git #versioning #branching #commit-message #conventional-commits #scopes

Ready to run

npx skills add https://github.com/yonderlab/kota.agent.skills --skill conventional-commit-yonderlab

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: conventional-commit
Source: https://github.com/yonderlab/kota.agent.skills/tree/main/skills/conventional-commit
Command: npx skills add https://github.com/yonderlab/kota.agent.skills --skill conventional-commit-yonderlab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforce consistent commit messaging by guiding users to create conventional commits.

Core Features & Use Cases

Enforce Conventional Commits across a repository to standardize history.
Validate branch naming to follow ticket prefix conventions.
Provide step-by-step guidelines for creating and pushing commits.

Quick Start

Create a conventional commit message for the changes, then push the feature branch.

Frequently Asked Questions about conventional-commit

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

FAQPage Schema

How do I write a conventional commit message for a bug fix?▼

A conventional commit message for a bug fix requires a specific structure using the fix type, optional scopes, and a descriptive body. This skill guides you through crafting these commit messages to enforce consistent messaging across your codebase.

What is the best way to enforce consistent git commit messages across multiple teams?▼

The best way to enforce consistent git commit messages is to standardize history using the Conventional Commits specification. This skill provides step-by-step guidelines for structuring types, scopes, and breaking changes for feature work and bug fixes.

Does this conventional commit tool validate git branch naming conventions?▼

Yes, this conventional commit tool validates branch naming to follow ticket prefix conventions. It ensures that your feature branches align with the required structure before you create and push commits.

How do I indicate a breaking change in a conventional commit?▼

To indicate a breaking change in a conventional commit, you must follow the specification's required structure for types, scopes, and breaking changes. This skill specifies the exact formatting needed to highlight breaking changes in your commit message.

Can I use conventional commits for documentation updates?▼

Yes, you can use conventional commits for documentation updates. This skill is applicable to feature work, bug fixes, and documentation updates across multiple branches and teams to maintain a standardized repository history.

What are the required components of a conventional commit message?▼

The required components of a conventional commit message include specific types, optional scopes, and breaking change notations. This skill guides you through specifying these structural elements per the Conventional Commits specification.