git-commit-formatter

Format git commit messages by enforcing a structured syntax that includes a type, scope, and description. This ensures all version control history adheres to the Conventional Commits specification for standardized logs.

The Conventional Commits specification is a standardized format for version control messages that uses types like fix or feat. It creates machine-readable commit logs by structuring messages with type, scope, and description.

To write a git commit message for a bug fix, use the fix type followed by a scope and description, such as fix(auth): resolve login redirect loop. This ensures structured, machine-readable version control logs.

Supported commit types for formatting git messages include features, fixes, docs, styles, refactors, performance improvements, tests, and chores. Each type structures the commit according to the Conventional Commits specification.

No dependencies are required to format conventional commit messages. The skill operates independently to enforce commit standards and structure your version control messages without external dependencies.

You should use structured commit messages in git to promote consistency and clarity in version control history. Standardized, machine-readable commit logs satisfy the need for automated parsing and organized project tracking.