commit-helper

What problem does it solve?

Inconsistent or poorly formatted Git commit messages can hinder code review, project history tracking, and automated release notes. This Skill ensures all commits adhere to the Conventional Commits specification, making your project history clean, understandable, and ready for automated tooling.

Core Features & Use Cases

• Conventional Commit Guidance: Provides clear rules for type, scope, and description (e.g., feat(ui): add dark mode toggle) to standardize your commit messages.
• Automated Analysis: Helps determine the correct commit type and scope by analyzing staged changes, reducing guesswork.
• Quality Gate Integration: Reminds you to run lint, test, and i18n:compare before committing, ensuring code quality and preventing regressions.
• Use Case: After implementing a new feature, activate this Skill to generate a perfectly formatted commit message that clearly communicates the change, its impact, and passes all quality checks, ready for a smooth Pull Request.

Quick Start

Stage your changes

git add <files>

Commit with a conventional message

git commit -m "type(scope): description"

Example with a body

git commit -m "$(cat <<'EOF' feat(ui): add user profile dashboard

This commit introduces a new user profile dashboard accessible from the top navigation bar. It displays user stats, badges, and customization options. EOF )"