git-commit-helper

Topics in the source

• Git Commit Helper
• Quick start
• Commit message format
• Types
• Examples
• Analyzing changes
• Commit message guidelines
• Multi-file commits

Analyze staged changes and generate commit message: Follow conventional commits format: feat: New feature fix: Bug fix docs: Documentation changes style: Code style changes (formatting, missing semicolons) refactor: Code refactoring test: Adding or updating tests chore: Maintenance tasks Feature commit: Bug fix: Refactor: Review what's being committed: DO: Use imperative mood ("add feature" not "added feature") Keep first line under 50 characters Capitalize first letter No period at end of summary Explain WHY not just WHAT in body DON'T: Use vague messages like "update" or "fix stuff" Include technical implementation details in summary Write paragraphs in summary line Use past tense When committing multiple related changes: Frontend: feat(ui): add loading spinner to dashboard fix(form): validate email format Backend: feat(api): add user profile endpoint fix(db): resolve connection pool leak Infrastructure: chore(ci): update Node version to 20 feat(docker): add multi-stage build Indicate breaking changes clearly: 1. Review changes: git diff --staged 2. Identify type: Is it feat, fix, refactor, etc.? 3. Determine scope: What part of the codebase? 4. Write summary: Brief, imperative d

This is an excerpt. Refer to the complete source and its current requirements.