skills.rest
ntk148v
ntk148vCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

conventional-commits

Generate conventional commit messages with type, scope, and breaking change markers.

1|1|Updated Feb 5, 2026
Search Tags:#git#conventional commits#semantic versioning#release automation#changelog generation#commit linting
One-click install
npx skills add https://github.com/ntk148v/skills --skill conventional-commits-ntk148v
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: conventional-commits
Source: https://github.com/ntk148v/skills/tree/main/skills/conventional-commits
Command: npx skills add https://github.com/ntk148v/skills --skill conventional-commits-ntk148v

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conventional Commits removes ambiguity in commit messages so tooling can reliably generate changelogs and determine semantic version bumps.

Core Features & Use Cases

  • Standardized commit message structure: Enforces a consistent pattern with type, optional scope, description, and optional body/footers for machine readability.
  • Semantic version impact mapping: Supports MINOR/patch behavior for feat and fix, and MAJOR behavior for breaking changes via ! or BREAKING CHANGE footers.
  • Release and automation readiness: Works with commit linting and release tools that generate CHANGELOGs and tags from commit history.

Quick Start

Use the conventional-commits skill when you need a commit message format that will support automated changelog and semantic release workflows.

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?▼

Standardized git commit messages enable automated changelog generation by enforcing a consistent pattern with a type, optional scope, description, and optional body or footers for machine readability.

What is conventional commits semantic version impact mapping?▼

Semantic version impact mapping determines version bumps based on commit types, applying MINOR or patch behavior for feat and fix, and MAJOR behavior for breaking changes encoded via ! or BREAKING CHANGE footers.

How do I indicate breaking changes in commit messages for semantic-release?▼

To indicate breaking changes for semantic-release pipelines, encode them in commit messages using an exclamation mark before the colon or by adding a BREAKING CHANGE footer.

Does this commit convention support optional scopes and bodies for CI checks?▼

Yes, this commit convention supports optional scopes and bodies, satisfying strict formatting requirements for type and description while enabling CI checks that enforce commit conventions across teams.

Why use standardized commit messages instead of free text for release automation?▼

Standardized commit messages remove ambiguity so tooling can reliably determine semantic version bumps and generate changelogs, whereas free text lacks the structure required for automated release workflows.

Can I use this commit format with existing commit linting pipelines?▼

Yes, this commit format works directly with commit linting and release tools, applying to git commit authoring across teams and CI checks that enforce commit conventions within existing pipelines.

Related Skills

Explore More Software Engineering Skills→
kamalsroor1kamalsroor1

speckit-git-initialize

Initialize a Git repository with an initial commit when none exists.

Community
Intermediate
FaysilAlshareefFaysilAlshareef
4

changelog-gen

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

Community
Intermediate
mvillmowmvillmow
18

generate-changelog

Generate a Markdown changelog from git commits grouped by conventional commit types.

Community
Basic
dennisonbertramdennisonbertram
1

changelog-gen

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

Community
Advanced