skills.rest
milistu
milistuCOMMUNITY
Explore all skills by this author →
Website𝕏@milistuuGitHub

conventional-commits

Generate conventional commit messages following the Conventional Commits v1.0.0 specification.

7|Updated Feb 2, 2026
Search Tags:#git#commit#formatting#semver#scope#conventional-commits#type
One-click install
npx skills add https://github.com/milistu/agent-skills --skill conventional-commits-milistu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: conventional-commits
Source: https://github.com/milistu/agent-skills/tree/main/skills/conventional-commits
Command: npx skills add https://github.com/milistu/agent-skills --skill conventional-commits-milistu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating conventional commit messages helps teams maintain a clear, machine-parseable history and improves release workflows by standardizing intent and scope.

Core Features & Use Cases

  • Enforces Conventional Commits v1.0.0 syntax with a standard type, optional scope, and a colon-separated description.
  • Supports common commit types (feat, fix, build, chore, ci, docs, style, refactor, perf, test) and optional breaking changes.
  • Improves release planning and changelog automation by providing structured commit messages.

Quick Start

Write a commit message like feat(auth): add login endpoint to improve 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 Conventional Commits v1.0.0 syntax with a standard type, optional scope, and colon-separated description to enable automated changelog generation. This structure enforces consistent history and clear intent for release workflows.

What are the supported conventional commit types for Angular-style formatting?▼

Supported conventional commit types for Angular-style formatting include feat, fix, build, chore, ci, docs, style, refactor, perf, and test. These types standardize commit intent and can optionally indicate breaking changes within the commit footer.

How do I write a conventional commit with a scope and description?▼

Write a conventional commit by combining a type, an optional scope in parentheses, and a colon-separated description, such as feat(auth): add login endpoint. This syntax ensures the commit message is machine-parseable and aligns with release planning requirements.

Does conventional commit formatting work for automated semantic versioning releases?▼

Conventional commit formatting works for automated semantic versioning releases by providing structured messages that indicate intent. Breaking changes and feature additions are explicitly marked, allowing automated tools to determine version bumps accurately.

When do I need to include breaking changes in a conventional commit message?▼

Include breaking changes in a conventional commit message when a feature or fix introduces modifications incompatible with previous versions. The skill supports optional breaking change sections in the footer to ensure clear release planning and accurate changelog automation.

Related Skills

Explore More Software Engineering Skills→
Hexsis-LLCHexsis-LLC
1

git-committer

Generate conventional one-line commit messages from git diffs.

Official
Intermediate
plurigridplurigrid
60

changelog-generator

Generate user-facing changelogs from git commit history.

Official
Advanced
timhiebenthaltimhiebenthal
17

commit-message-creator

Lint git commit messages against the Conventional Commits specification.

Community
Intermediate
dennisonbertramdennisonbertram
1

changelog-gen

Generate release notes from Git history using Conventional Commits and git-cliff.

Community
Advanced