How does the Commit Message Helper work?

The skill runs 'git diff --staged' to analyze your current changes and then generates a suggested message following Conventional Commit standards.

What commit types are supported?

It supports a wide range of types including feat, fix, docs, style, refactor, perf, test, build, and ci.

Does it follow git best practices?

Yes, it uses the present tense, keeps summaries under 50 characters, and explains the 'what' and 'why' of the changes rather than the 'how'.

Can I use this for reviewing changes?

Absolutely. It's an excellent tool for summarizing staged changes to ensure you are committing exactly what you intended.

Commit Message Helper

Name: Commit Message Helper
Author: tom237ttkk

bytom237ttkk

Developer Tools

Generates structured, professional Git commit messages by analyzing staged changes and applying industry-standard formatting.

About

The Commit Message Helper skill streamlines your version control workflow by automatically interpreting staged code changes and crafting clear, concise commit messages. By analyzing the output of git diffs, it generates messages that follow the Conventional Commits specification, including specific prefixes like feat, fix, and refactor. This skill ensures your project history remains readable and professional by focusing on the purpose of the change while adhering to strict formatting constraints like the 50-character summary limit.

Key Features

0 GitHub stars
Character-limited summary line optimization
Present-tense imperative formatting
Conventional Commits type tagging (feat, fix, docs, etc.)
Automated git diff analysis for staged changes
Contextual component identification

Use Cases

Drafting detailed commit descriptions for complex pull requests
Standardizing commit history across a multi-developer project
Reviewing staged changes before finalizing a git commit

About

Key Features

0 GitHub stars
Character-limited summary line optimization
Present-tense imperative formatting
Conventional Commits type tagging (feat, fix, docs, etc.)
Automated git diff analysis for staged changes
Contextual component identification

Use Cases

Drafting detailed commit descriptions for complex pull requests
Standardizing commit history across a multi-developer project
Reviewing staged changes before finalizing a git commit