git-commit-format

To format Git commit messages for automated changelog generation, use the Conventional Commits specification by structuring messages as `type(scope): description`. This standardization makes commits machine-readable, satisfying semantic versioning requirements and enabling automated changelog creation.

The Conventional Commits format for Git history requires structuring messages as `type(scope): description`. It uses specific commit types like `feat`, `fix`, and `docs` to categorize changes, providing clear definitions for scopes to make project history searchable and clear.

To enforce standard commit types like `feat` and `fix` in your developer workflow, apply a skill that prompts for Conventional Commits formatting during code commits. This ensures each commit message adheres to the structured `type(scope): description` format automatically.

No dependencies are required to enforce Conventional Commits in your project. The skill operates independently to guide the agent in standardizing commit types, scopes, and body content without needing external tools or version control plugins.

You should use scopes in your Git commit messages when you need to specify the module or component affected by a code change. Scopes are placed in parentheses within the `type(scope): description` format to provide additional context and improve code hygiene.

Code hygiene rules for semantic versioning are designed for Git commit messages. They apply the Conventional Commits standard to any code commits requiring structured messages, ensuring the version control history remains clear and machine-readable.