git-commit-messages

Enforce conventional commit standards with subject, body, and footer rules.

Updated Nov 15, 2025
One-click install
npx skills add https://github.com/CowboyLogic/ai-dev --skill git-commit-messages-cowboylogic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit-messages
Source: https://github.com/CowboyLogic/ai-dev/tree/main/skills/git-commit-messages
Command: npx skills add https://github.com/CowboyLogic/ai-dev --skill git-commit-messages-cowboylogic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent commit messages hinder traceability and collaboration; this guide provides rules and templates to enforce a standard across projects, and examples to illustrate good practices.

Core Features & Use Cases

  • Conventional commit types (feat, fix, docs, style, refactor, test, chore, perf, ci, build)
  • Subject line rules (≤50 characters, imperative mood, no trailing punctuation)
  • Body formatting guidelines (wrap at 72 characters, use bullets, reference issues)
  • Automation integration (commit-generator.py, VS Code integration, and Git hooks) with practical workflows

Quick Start

Stage changes, then generate and apply a conventional commit message using the built-in generator or VS Code integration.

Frequently Asked Questions about git-commit-messages

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

FAQPage Schema
How do I enforce conventional commit standards for git commit messages?

You can enforce conventional commit standards by applying rules for commit types, subject length, imperative mood, body formatting, and issue references. This skill provides templates and a generator script to automate message creation.

What are the rules for a valid conventional commit subject line?

A valid conventional commit subject line must be 50 characters or less, use imperative mood, and omit trailing punctuation. These rules improve traceability and consistency across software projects during code reviews.

Can I automate git commit message generation in VS Code?

Yes, you can automate git commit message generation in VS Code using the built-in integration and generator script. Stage your changes, then apply the automated guidance to generate a properly formatted conventional commit message.

How do I format breaking changes and issue references in commit messages?

Format breaking changes and issue references in the commit body by wrapping text at 72 characters and using bullets. Specific footer guidelines ensure breaking changes and issue tracking references are clearly documented for traceability.

Does this conventional commit approach work with CI hooks?

Yes, this conventional commit approach integrates with CI hooks and Git hooks. Applying these standards during commit creation and automation ensures consistent traceability across your software projects.