conventional-commits

Name: conventional-commits
Availability: InStock
Author: VibeKit

Format and validate Git commit messages using the Conventional Commits specification.

Updated Aug 27, 2026

Search Tags:#git #versioning #commits #lint #format #conventional-commits

Ready to run

npx skills add https://github.com/vibekit-apps/skills-registry --skill conventional-commits-vibekit-apps

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: conventional-commits
Source: https://github.com/vibekit-apps/skills-registry/tree/main/skills/conventional-commits
Command: npx skills add https://github.com/vibekit-apps/skills-registry --skill conventional-commits-vibekit-apps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Format commit messages using the Conventional Commits specification to enable automated tooling, consistent changelogs, and reliable versioning.

Core Features & Use Cases

Enforce header format: type(scope): description
Validate body and footers for breaking changes and references
Improve history readability and automation across CI/CD

Quick Start

Write a sample commit message following the format, for example: feat(auth): add user authentication

Frequently Asked Questions about conventional-commits

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

FAQPage Schema

How do I format git commit messages for automated changelog generation?▼

Format git commit messages using the Conventional Commits specification to enable consistent changelogs and automated versioning. This structure enforces a specific header format of type(scope): description to ensure compatibility across CI/CD pipelines.

What is the correct conventional commit format for indicating a breaking change?▼

The conventional commit format indicates a breaking change by adding a `!` after the type or scope, or by including a `BREAKING CHANGE:` footer in the commit body. This ensures automated tooling correctly identifies major version bumps.

How do I validate the body and footers of a conventional commit message?▼

Validate conventional commit body and footers by checking against the specification's rules for breaking changes and references. This ensures the type, scope, and body formatting meet the required automated tooling compatibility standards.

Do I need to specify a scope in every conventional commit message?▼

Specifying a scope in a conventional commit message is optional. The spec enforces the required type and description, but the scope within the parentheses can be omitted while maintaining automated tooling compatibility.

Can I use conventional commits to rewrite existing git history?▼

Yes, you can apply conventional commits formatting when rewriting git history. The specification ensures header format, body, and footer validation remain consistent across various Git workflows.

What types of commit messages are enforced by the Conventional Commits spec?▼

The Conventional Commits spec enforces specific types like `feat` and `fix` to standardize versioning. These types dictate automated semantic version bumps and improve overall history readability across CI/CD pipelines.