commit-helper

To generate a conventional commit message, provide your current git diff or staged changes. The Skill analyzes code changes, categorizes them by type, detects breaking changes, and formats the output to comply with the Conventional Commits specification.

A conventional commit message follows a standardized format categorizing changes by type, scope, and breaking impact. You need it to automate versioning and streamline documentation in software projects using the Conventional Commits specification.

Yes, conventional commits can detect breaking changes by analyzing your staged and unstaged code differences. The Skill identifies critical modifications and indicates the required major version impact for your project.

Yes, the commit message generator integrates with existing git workflows by analyzing staged and unstaged changes. It streamlines commits for features, fixes, docs updates, and refactors without disrupting your development process.

The best way to categorize refactors and docs updates is by applying the Conventional Commits specification to your git diff. The analysis identifies the specific change type and suggests an appropriate scope and version impact.

You do not need to stage all files because the analysis evaluates both staged and unstaged changes. Providing the current git diff allows the Skill to accurately detect features, fixes, and breaking changes for the commit message.