commit-message-helper

To write a Git commit message following Conventional Commits, structure it using the format `<type>(<scope>): <subject>` followed by a body and footer. The commit message helper guides you through defining each section to ensure a standardized, machine-readable code history.

Standard commit types in Conventional Commits include feat, fix, docs, style, refactor, perf, test, and chore. Each type categorizes the nature of your code changes, such as using feat for new features or fix for bug resolutions.

Git commit subject lines should be concise, written in the imperative mood, and separated from the body by a blank line. Following these formatting rules ensures your commit history remains standardized and highly readable.

To generate a commit message for a bug fix, use the fix type, define the scope, and write an imperative subject line like `fix: resolve login button alignment issue`. You can then add a detailed body explaining the resolution.

A standardized Git commit history improves code readability and enables automation. By adhering to the Conventional Commits specification, your commit messages become machine-readable, allowing for automated versioning and changelog generation.