conventional-commits

Name: conventional-commits
Availability: InStock
Author: punkfuncgames

Standardize git commit messages using the Conventional Commits format.

Updated Aug 27, 2026

Search Tags:#git #changelog #commitlint #semantic-versioning #conventional-commits #commit-messages

Ready to run

npx skills add https://github.com/punkfuncgames/tetris-clone --skill conventional-commits-punkfuncgames

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent or vague git commit messages make code review, changelog generation, and automatic versioning unreliable; this guide provides a strict, machine-friendly format to make history discoverable and meaningful.

Core Features & Use Cases

Formalized Commit Format: Defines required type, optional scope, imperative subject, body and footer conventions to create predictable commit entries.
Breaking Change & Scope Handling: Explains how to mark breaking changes and choose module scopes to support safe refactors and automated releases.
Use Case: Teams preparing release notes and automated semantic version bumps can follow these rules to generate changelogs and integrate with CI/CD tools.

Quick Start

Use the conventional-commits guide to write commit messages like feat(ui): add dark mode toggle when introducing new user-facing features.

Frequently Asked Questions about conventional-commits

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

FAQPage Schema

What is the conventional commits format for git commit messages?▼

The conventional commits format standardizes git commit messages using a required type, optional scope, imperative subject, body, and footer to make commit history machine-parseable for automated tooling.

How do I write a git commit message for automated semantic versioning?▼

To write a git commit message for semantic versioning, structure it with a type like feat or fix, an optional scope, and a descriptive subject, such as feat(ui): add dark mode toggle, to trigger automated version bumps.

How do I mark breaking changes in commit messages for changelog generation?▼

Mark breaking changes in commit messages by adding a footer with a BREAKING CHANGE marker or appending an exclamation mark after the type, ensuring safe refactors and automated releases update the changelog accordingly.

Can I use conventional commits for PR titles in CI-driven release automation?▼

Yes, conventional commits can be applied to PR titles in CI-driven release automation, providing a strict, machine-friendly format that ensures consistent changelog generation and reliable semantic version bumps.

Why does inconsistent git commit history break changelog generation?▼

Inconsistent git commit history breaks changelog generation because vague messages lack the machine-readable type, scope, and breaking-change markers required by automated tools to reliably parse changes and generate release notes.

Do I need commitlint to enforce conventional commit messages?▼

Commitlint is commonly used to enforce conventional commit messages in team repositories, ensuring entries follow the required type, scope, and imperative subject rules for predictable automated releases.