create-git-commit

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.

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.

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.

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.

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.

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.