git-conventional

You can generate conventional commits messages by analyzing your git diff to determine the commit type, scope, and description. This skill infers scope from modified file paths and crafts imperative-style descriptions for standardized code history.

The conventional commits specification standardizes git commit messages using structured types like feat or fix. Adopting it ensures consistency and clarity in your project history, enabling automated detection of breaking changes and scope from file paths.

Automatic detection of breaking changes is supported by analyzing code differences during commit message generation. The skill evaluates the diff to flag breaking changes and infers the appropriate scope from modified file paths.

Yes, you can infer the commit scope from file paths in your git changes. The skill analyzes modified file paths to suggest the appropriate scope, such as generating a message like feat(auth): implement two-factor authentication for an auth module update.

No, this conventional commits generator requires no external dependencies. It operates as a standalone skill with scripts and references to analyze code differences and produce standardized commit messages without additional environment setup.

The best way to automate standardizing git commit types is to analyze code diffs to suggest the appropriate type, such as feat, fix, or docs. This skill evaluates your changes and generates imperative-style descriptions adhering to the conventional commits specification.