skills.rest
darellchua2
darellchua2COMMUNITY
Explore all skills by this author →
Website𝕏@DarellChua2GitHub

git-semantic-commits

Formats Git commit messages to the Conventional Commits specification with MAJOR/MINOR/PATCH impact guidance.

4|4|Updated Jan 15, 2026
Search Tags:#git#workflow#commitlint#semantic-release#semantic-versioning#conventional-commits#format-commits
One-click install
npx skills add https://github.com/darellchua2/opencode-config-template --skill git-semantic-commits
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-semantic-commits
Source: https://github.com/darellchua2/opencode-config-template/tree/main/skills/git-semantic-commits
Command: npx skills add https://github.com/darellchua2/opencode-config-template --skill git-semantic-commits

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces Conventional Commits formatting and aligns messages with semantic versioning to improve changelogs and release planning.

Core Features & Use Cases

  • Format as you type: Suggests or formats commit messages to the <type>(<scope>): <subject> pattern.
  • Type detection & versioning: Infers MAJOR/MINOR/PATCH impact for release notes and automation.
  • Template generation & validation: Provides templates for each type and integrates with tooling like commitlint or semantic-release.

Quick Start

Format a sample commit, e.g., feat(auth): add OAuth2 support for third-party providers

Frequently Asked Questions about git-semantic-commits

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

FAQPage Schema
How do I format Git commit messages to follow conventional commits?▼

Format Git commit messages using the <type>(<scope>): <subject> pattern to align with conventional commits. This structure ensures standardized messages, improving automated changelog generation and release planning.

How does conventional commit formatting determine semantic versioning impact?▼

Semantic versioning impact is determined by parsing commit types to infer MAJOR, MINOR, or PATCH changes. Breaking changes trigger a MAJOR version bump, new features trigger MINOR, and fixes trigger PATCH.

Can I use commitlint and semantic-release with conventional commit formatting?▼

Yes, conventional commit formatting integrates with commitlint and semantic-release. It provides templates and validates subjects to ensure messages comply with tooling requirements for automated versioning and release workflows.

What is the best way to handle breaking changes in conventional commit messages?▼

Handle breaking changes in conventional commit messages by appending a ! after the type/scope or including a BREAKING CHANGE footer. This syntax ensures the semantic versioning tooling correctly identifies and processes the MAJOR version impact.

Why do I need standardized Git commits for my development workflow?▼

Standardized Git commits are needed to improve changelogs and release planning. By enforcing a consistent type and scope format, teams can automatically generate structured release notes and track version impacts accurately.

Does git semantic commits validate the subject line of my commit messages?▼

Yes, git semantic commits validates the subject line of your commit messages. It enforces standardized templates and checks the subject against conventional commits rules to ensure proper formatting for semantic versioning awareness.

Related Skills

Explore More Software Engineering Skills→
vndkubivndkubi

conventional-commit

Generate conventional commit messages from staged changes.

Community
Intermediate
AstrumonAstrumon

changelog-generator

Generate Keep a Changelog entries from Conventional Commits history.

Community
Intermediate
ehtbantonehtbanton

commitlint-config-generator

Generate commitlint configuration files enforcing Conventional Commits 1.0.0 standards.

Community
Basic
vulikjulikvulikjulik

aif-commit

Generate conventional commit messages from staged git changes.

Community
Intermediate