conventional-commits

Name: conventional-commits
Availability: InStock
Author: kensledev

Generate Conventional Commits messages with structured types, scopes, and footers.

Updated Oct 14, 2025

Search Tags:#git #changelog #code review #versioning #conventional commits #commits

Ready to run

npx skills add https://github.com/kensleDev/dotfiles --skill conventional-commits-kensledev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: conventional-commits
Source: https://github.com/kensleDev/dotfiles/tree/main/claude/.claude/skills/conventional-commits
Command: npx skills add https://github.com/kensleDev/dotfiles --skill conventional-commits-kensledev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you create clear, consistent, and machine-readable commit messages, improving code review, automation, and project history.

Core Features & Use Cases

Structured Commits: Enforces a standard format (type(scope): subject) for commit messages.
Clear Intent: Differentiates between features, fixes, documentation, and other changes.
Use Case: When contributing to a team project, use this Skill to ensure your commits follow the established Conventional Commits standard, making it easier for others to understand your changes and for automated tools to generate changelogs.

Quick Start

Follow the Conventional Commits format to write your next commit message.

Frequently Asked Questions about conventional-commits

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

FAQPage Schema

What are conventional commits and how do they structure git commit messages?▼

Conventional commits structure git commit messages using a standard format like `type(scope): subject`, differentiating between features, fixes, and documentation changes to create human-readable and machine-parseable project histories.

How do I write a structured commit message for a breaking change?▼

To write a structured commit message for a breaking change, use the conventional commits format and include specific breaking change annotations within the commit body or footer, often alongside issue tracking references.

How do conventional commits improve automated changelog generation?▼

Conventional commits improve automated changelog generation by enforcing a semantic, machine-parseable message format, allowing automated tools to easily extract structured types, scopes, and subjects to build project histories.

Can I use conventional commits for code review in any software development workflow?▼

Yes, you can use conventional commits in any software development workflow to standardize commit messages, providing clear intent for code review regardless of the specific platform or project scale.

What is the best way to standardize commit messages for team projects?▼

The best way to standardize commit messages for team projects is adhering to the conventional commits specification, utilizing structured commit types, scopes, subjects, bodies, and footers to ensure consistent and readable project histories.

Why should I include a scope in my conventional commit message?▼

You should include a scope in your conventional commit message to specify the module or component affected by the change, adding an extra layer of semantic clarity for code review and project history tracking.