commit-helper

Conventional commit messages follow a standardized format with type, scope, and subject. Feed your staged diff to commit-helper using `git diff --staged | commit-helper` to automatically generate a formatted message with a summary under 50 characters, blank line, and detailed body describing the why behind your changes.

Conventional commits are standardized messages using types like feat, fix, refactor, docs, test, and chore. They reduce ambiguity in commit history, enable automated changelog generation, and make code review clearer by explicitly stating whether changes add features, fix bugs, or address maintenance tasks.

Yes. Conventional commits enable automated release note generation by parsing commit type and scope. Standardized messages from commit-helper produce structured data that tools can extract and organize by feature, fix, and chore categories for consistent changelog output.

Commit-helper enforces the 50-character subject line limit automatically when generating conventional commit messages from diffs. This constraint keeps commit summaries concise and scannable in logs while the detailed body provides the full context and rationale.

Conventional commits support scope and footer sections to list affected components. Commit-helper generates suggestions for type, scope, and optional footers so you can document which modules or features your diff impacts, improving traceability across your codebase.