create-git-commit

Enforce standardized git commit messages with type, scope, and description.

Updated Oct 25, 2025

Search Tags:#code quality #git #developer tools #version control #software development #commit messages

Ready to run

npx skills add https://github.com/WesleyMFrederick/cc-workflows --skill create-git-commit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-git-commit
Source: https://github.com/WesleyMFrederick/cc-workflows/tree/main/.claude/skills/create-git-commit
Command: npx skills add https://github.com/WesleyMFrederick/cc-workflows --skill create-git-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents inconsistent and vague commit messages that hinder project history, automated changelog generation, and semantic versioning, making code maintenance difficult.

Core Features & Use Cases

Mandatory Format Enforcement: Ensures all commits adhere to a strict type(scope): description structure, enabling machine-parsable history.
Scope Discovery: Guides you in identifying the correct scope from codebase changes, preventing ambiguity and promoting consistency.
AI Attribution: Automatically includes AI coding assistant attribution in commit footers, maintaining transparency.

Quick Start

Use the create-git-commit skill to generate a commit message for my staged changes.

Frequently Asked Questions about create-git-commit

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

FAQPage Schema

How do I enforce standardized commit messages across my team?▼

Standardized commit messages enforce a consistent `type(scope): description` format across all commits, enabling machine-parsable history and automated changelog generation. This Skill mandates the format by validating type, scope, and description in every commit, preventing vague messages that hinder project maintenance.

What commit message format should I use for version control?▼

The format `type(scope): [US#.#] [Task #.#.#] description` structures commits for semantic versioning and automated processing. Type and scope are mandatory, scope is discovered from codebase changes, and description must clearly convey the work performed.

How can I automate changelog generation from git commits?▼

Machine-parsable commit messages with standardized type, scope, and description enable automated changelog generation and semantic versioning. This Skill enforces that structure so changelog tools can reliably extract and organize commits by type and scope.

Can I include AI attribution in my commit messages?▼

Yes. This Skill automatically includes AI coding assistant attribution in commit footers, maintaining transparency about which commits involved AI-assisted development while keeping the core message format clean.

How does scope discovery work in commit validation?▼

Scope is discovered by analyzing staged changes using `git status` and `git diff --name-only` against your codebase structure. This prevents scope bypass and ensures the scope reflects the actual files modified in each commit.

What problems do inconsistent commit messages cause?▼

Vague or inconsistent commits hinder project history review, break automated changelog generation, prevent semantic versioning, and make code maintenance and debugging difficult. Standardized format solves these issues across feature work, bug fixes, refactors, and documentation.