dev-commit-writer

To generate a commit message for code changes, analyze current unstaged and staged modifications to produce a clear, style-consistent summary. This process detects unrelated modifications and suggests splitting them into multiple commits for accurate version control history.

Commit message generation matches repository style by analyzing existing commit history and conventions. It uses your past formatting patterns to produce style-consistent messages that integrate seamlessly with your current project documentation standards.

Yes, you can generate a commit message for specific staged files or a particular path. By optionally specifying the target files, the message generation focuses solely on those code changes to provide an accurate and concise summary.

To handle unrelated modifications when preparing a commit, the generation process analyzes scope and detects incidental changes. It suggests splitting unrelated code changes into multiple separate commits to maintain clear project history documentation.

The best way to automate git commit messages for self-reviewed changes is generating them from current code modifications. This ensures style-consistent documentation by analyzing staged and unstaged differences while detecting unrelated modifications for splitting.