git-commit-helper_skill

Overview

This skill generates descriptive, conventional commit messages by analyzing staged git diffs. It recommends commit type, scope, concise summary, and a focused body that explains why the change was made. Use it to produce consistent, human-friendly commits that follow best practices for traceability and code review.

How this skill works

The skill inspects staged changes (git diff --staged) to determine file groups, modified functions, and intent (feature, fix, docs, refactor, test, style, chore). It suggests a conventional-commits formatted message: <type>(<scope>): <summary> plus an optional body and footer for issue references or breaking changes. The output emphasizes imperative mood, a sub-50 character summary, and a body that explains rationale and impact.

When to use it

• Preparing a commit from staged changes
• Needing a consistent conventional-commit message
• Writing summaries for code review or CI changelogs
• Refining vague or terse commit messages
• Adding issue references or noting breaking changes

Best practices

• Make commits atomic—one logical change per commit
• Choose the most specific type and scope that apply
• Keep the summary under 50 characters and use imperative mood
• Use the body to explain why and the impact, not low-level implementation
• Reference issue numbers and clearly mark breaking changes

Example use cases

• Generate a commit message for a new authentication feature across multiple files
• Create a concise fix commit after stabilizing a failing unit test
• Convert a terse staged change into a conventional-commits formatted message with scope and body
• Draft a chore commit for dependency bumps or build tooling changes
• Annotate a refactor commit to explain design decisions and ensure reviewers understand intent