skills.rest
t0lab
t0labOFFICIAL
Explore all skills by this author →
WebsiteGitHub

git-conventional

Enforce Conventional Commits formatting and map commit types to semantic version bumps.

2|Updated Apr 10, 2026
Search Tags:#git#changelog#semver#commit-message#conventional-commits#commit-guidelines
One-click install
npx skills add https://github.com/t0lab/harness-kit --skill git-conventional-t0lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-conventional
Source: https://github.com/t0lab/harness-kit/tree/main/.agents/skills/git-conventional
Command: npx skills add https://github.com/t0lab/harness-kit --skill git-conventional-t0lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many teams and projects suffer from inconsistent commit messages and unclear release implications; this Skill provides a clear, repeatable commit message format and maps commit types to semantic version changes so history and releases remain predictable.

Core Features & Use Cases

  • Standardized Format: Defines the Conventional Commits structure (type, optional scope, optional breaking marker, short description, optional body and footers) to keep messages uniform.
  • Semver Mapping: Explains how commit types map to semantic version bumps (fix → patch, feat → minor, feat! or BREAKING CHANGE → major).
  • Practical Rules & Examples: Advises on subject length, imperative tone, body guidance, scope conventions, and common types for real-world use.
  • Use Cases: Compose or suggest commit messages before committing, audit or clean a project's git history, and determine release impact for CI-driven versioning.

Quick Start

Create a Conventional Commit message for adding OAuth2 refresh token support in the auth module, following the git-conventional rules and indicating whether it is a breaking change.

Frequently Asked Questions about git-conventional

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

FAQPage Schema
How do I format conventional commit messages for git?▼

Conventional commit messages require a structure of type, optional scope, breaking-change marker, short description, body, and footers. This keeps git history uniform and predictable across team projects.

How do conventional commits map to semantic version bumps?▼

Semantic version bumps map directly from commit types: fix triggers a patch, feat triggers a minor, and feat! or a BREAKING CHANGE footer triggers a major version increment in CI pipelines.

What is the best way to indicate a breaking change in a commit message?▼

Indicate a breaking change in a commit message by appending a ! after the scope or by adding a BREAKING CHANGE footer. This explicitly maps the commit to a major semantic version bump.

Does git-conventional enforce specific commit types and subject length limits?▼

Yes, git-conventional enforces common commit types, imperative tone, and subject length limits. It provides practical rules for scope conventions to keep commit messages uniform.

When do I need to use conventional commits in my project?▼

You need conventional commits when composing messages before git commit, auditing git history, or determining release impact for CI-driven semantic versioning to ensure predictable releases.

Can I use conventional commits to audit and clean an existing git history?▼

Yes, you can apply conventional commit rules to audit and clean an existing git history. The standardized format clarifies past changes and their semantic version implications.

Related Skills

Explore More Software Engineering Skills→
cptnfrencptnfren
3

localsetup-automatic-versioning

Automate version bumps from conventional commits and update VERSION, READMEs, and docs.

Community
Advanced
FaysilAlshareefFaysilAlshareef
4

changelog-gen

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

Community
Intermediate
drgaciwdrgaciw

changelog-automation

Generate changelogs and release notes from Conventional Commits in CI/CD pipelines.

Community
Intermediate
JannaelJannael
16

caveman-commit

Generates Git commit messages adhering to Conventional Commits format with strict subject and body rules.

Community
Intermediate