Commit message generator

Skill bg-szy/TOP-SKILLS/skills/marketplace/commit-message-generator

全球最大的 Claude Code 技能聚合库 · 收录 3900+ 来自 12+ 来源的技能，提供在线搜索与趋势分析看板 / The world's largest Claude Code skill aggregation hub — 3900+ skills from 12+ sources with online search and trend dashboard

Install

npx -y skills add bg-szy/TOP-SKILLS --skill commit-message-generator

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Generate appropriate commit messages based on Git diffs

SKILL.md

1.5 KB, 305 tokens by cl100k_base, as published. Nobody here has run it

Prerequisites

This Skill retrieves Git diffs and suggests meaningful commit messages
Message format should follow Conventional Commits
Commit messages should have a one-line Conventional Commits header, an optional blank second line, and from the third line onward include a bulleted list summarizing the changes
Commit messages should be in English
Never perform Git commit or Git push

Steps

Run git status to check modified files
Retrieve diffs with git diff or git diff --cached
Analyze the diff content and determine if changes should be split into multiple commits
For each logical group of changes:
- List the target files
- Generate a message in English compliant with Conventional Commits
- Suggest the command: git add <files> && git commit -m "<message>"
If changes are extensive and should be split, provide:
- Rationale for the split
- Multiple commit suggestions with their respective target files and messages

Commit Splitting Guidelines

Split commits when changes span multiple logical concerns (e.g., feature + refactoring)
Group related files that serve the same purpose
Keep each commit focused on a single, atomic change

Notes

This Skill must never execute git commit or git push
Only suggest commands; execution is entirely at user's discretion
Users must explicitly perform commits and pushes themselves