git-commit-helper

To generate conventional commit messages from staged git changes, stage your files and run the skill. It parses the diff to extract file changes, infers the appropriate type and scope, and outputs a standardized commit string.

Yes, you can detect the correct commit scope in a monorepo with multiple packages. The skill analyzes staged git changes and infers the scope directly from the monorepo packaging structure to ensure accurate conventional commits.

Breaking change detection for conventional commits works by analyzing staged file diffs for potential breaking modifications. When detected, the skill surfaces these changes directly in the commit message or appends a BREAKING CHANGE footer.

The best way to automate type prefixes like feat or fix in git commits is to parse staged diffs for file modifications. The skill evaluates the changes to determine the correct conventional commit type prefix automatically.

Yes, this conventional commit generator works without external dependencies. It relies solely on your local staged git changes, using a built-in diff parser to analyze file modifications and output the standardized commit string.

You need a BREAKING CHANGE footer in your conventional commit when staged git changes introduce backward-incompatible modifications. The skill identifies these potential breaking changes during diff analysis and formats the footer accordingly.