git-committer

You can generate a conventional commit message by analyzing your staged changes, unstaged modifications, and untracked files using this Skill, which outputs single-line summaries and suggests multiple commits for extensive changes.

The best way to write commit messages for untracked and unstaged files is to analyze the git status and diff comprehensively, which this Skill does by providing suggestions for multiple commits when your code modifications are extensive.

Yes, this commit message generator supports conventional commit standards to ensure consistency and clarity in your project's version control history by formatting single-line messages based on your actual git changes.

Yes, you can use historical commit messages to improve generation accuracy, as this Skill analyzes your past commit history alongside current git status and diffs to create contextually accurate conventional commit messages.

To handle extensive code changes, this Skill analyzes the full git diff and provides suggestions for multiple commits rather than forcing a single message, ensuring each logical change receives an accurate conventional commit summary.