skills.rest
metalagman
metalagmanCOMMUNITY
Explore all skills by this author →
GitHub

conventional-commits

Generate and validate commit messages conforming to the Conventional Commits specification.

21|1|Updated Jan 8, 2026
Search Tags:#automation#linting#versioning#semantic#commit-message#conventional-commits
One-click install
npx skills add https://github.com/metalagman/agent-skills --skill conventional-commits-metalagman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: conventional-commits
Source: https://github.com/metalagman/agent-skills/tree/main/conventional-commits
Command: npx skills add https://github.com/metalagman/agent-skills --skill conventional-commits-metalagman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

Writing consistent, machine-readable commit messages is error-prone and hampers changelog automation across teams.

Core Features & Use Cases

  • Draft semantic commit messages that follow the Conventional Commits specification.
  • Validate and transform existing commits to ensure they adhere to the format for features, fixes, and chores.
  • Generate consistent messages across multi-repo projects to support automated changelog generation.

Quick Start

Draft a conventional commit message for the latest change in your codebase following the Conventional Commits rules.

Frequently Asked Questions about conventional-commits

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

FAQPage Schema
How do I write semantic commit messages that conform to the Conventional Commits specification?▼

To write semantic commit messages, format them as <type>[optional scope]: <description>. This enforces lowercase types, omits trailing periods, and supports optional BREAKING CHANGE footers to ensure machine readability.

How can I validate and fix existing commit messages to follow a machine-readable format?▼

You can validate and transform existing commit messages to follow the Conventional Commits format. The skill checks messages for features, fixes, docs, and chores, ensuring they adhere to the required semantic structure.

Why do I need conventional commit messages for automated changelog generation?▼

Automated changelog generation requires consistent, machine-readable commit messages. Enforcing the Conventional Commits specification standardizes entries across features and fixes, preventing manual formatting errors that hampers changelog automation across teams.

Can I enforce consistent commit messages across multi-repo software projects?▼

Yes, you can generate consistent semantic commit messages across multi-repo projects. This standardizes the <type>[optional scope]: <description> format across all repositories to support reliable automated changelog generation.

What are the limitations of enforcing semantic commit messages for existing commits?▼

The limitations of enforcing semantic commit messages involve strict adherence to Conventional Commits rules. Messages must use lowercase types, no trailing periods, and correctly formatted BREAKING CHANGE footers for validation to pass.

Related Skills

Explore More Software Engineering Skills→
xjiang77xjiang77

commit

Generate conventional Git commit messages with Chinese descriptions from staged changes.

Community
Intermediate
FaysilAlshareefFaysilAlshareef
4

changelog-gen

Generate changelogs from git commits using Conventional Commits and Keep a Changelog formats.

Community
Intermediate
AmidVoshakulAmidVoshakul

git-hooks-automation

Automate Git hook configuration for linting, formatting, and commit message validation.

Community
Advanced
missdeermissdeer

commit

Create local git commits with conventional commit message formatting.

Community
Intermediate