Commit
- 2 installs
- 2.2k repo stars
- Updated July 27, 2026
- alibaba/loongcollector
commit is a Claude skill that generates Conventional Commits messages from staged changes with strict type, subject, and body formatting.
About
This skill generates commit messages that follow the Conventional Commits specification. A developer uses it to turn staged changes into a structured message with a type, optional scope, imperative subject under 50 characters, a wrapped body, and an optional footer. It reads git diff to determine the commit type and prohibits vague messages like update code or wip.
- Generates commit messages following the Conventional Commits spec
- Enforces type/scope/subject/body/footer format with length limits
- Reads git diff to determine commit type and subject
Commit by the numbers
- 2 all-time installs (skills.sh)
- +1 installs in the week ending Jun 23, 2026 (Skillselion tracking)
- Ranked #498 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
commit capabilities & compatibility
- Capabilities
- documentation
- Works with
- github
- Use cases
- documentation
- Pricing
- Free
What commit says it does
Generate commit messages that follow the Conventional Commits specification.
No meaningless descriptions like "update code", "fix bug", "wip"
npx skills add https://github.com/alibaba/loongcollector --skill commitAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2 |
|---|---|
| repo stars | ★ 2.2k |
| Last updated | July 27, 2026 |
| Repository | alibaba/loongcollector ↗ |
What it does
Write a Conventional Commits message from staged changes with proper type, scope, subject, and body.
Who is it for?
Developers who want consistent Conventional Commits messages generated from their git diff
Skip if: Vague one-line commits like 'update code' or 'wip', which the skill explicitly forbids
When should I use this skill?
When writing a commit message for staged changes
What you get
A well-formed Conventional Commits message with correct type, scope, subject, and body
- Conventional Commits message
By the numbers
- 9 commit types (feat, fix, docs, style, refactor, perf, test, chore, revert)
- subject <= 50 chars, body lines <= 72 chars
Files
Commit Skill
Generate commit messages that follow the Conventional Commits specification.
Format
type(scope): verb + object
{why is this change needed, what user/system impact it brings}
Fixes #{ISSUE_ID}Fields
- type:
feat | fix | docs | style | refactor | perf | test | chore | revert - scope: Optional. File/module/subsystem, e.g.
api,ui,auth,deps - subject: <= 50 characters, imperative mood, lowercase first letter, no period
- body: Each line <= 72 characters. Explain "what" and "why"
- footer: Optional. Link Issue / PR / Breaking Change
Steps
1. Collect information by reading git diff. Skip if user already provided context. 2. Determine the commit type based on changes. 3. If changes span multiple scopes, use the core module as scope. 4. Extract added/modified/deleted functions, classes, interfaces for the subject. 5. If breaking change, add BREAKING CHANGE: to footer. 6. Present the complete commit message for user confirmation before executing git commit.
Prohibited
- No meaningless descriptions like "update code", "fix bug", "wip"
- No subject or body lines exceeding 72 characters
- No issue links in the subject line
Related skills
Caveman CommitGenerate terse, Conventional Commits messages that preserve intent without fluff or AI attribution.272k94k
Resolving Merge ConflictsQuickly understand, resolve, and commit merge conflicts without losing work or breaking their flow.183k193kGit Guardrails Claude CodePrevent Claude Code from accidentally running destructive git commands like force push, hard reset, or clean.175k193k
Using Git WorktreesGuarantee every new feature or implementation task runs inside a clean, isolated workspace without polluting the main branch or current working directory.149k263k
Git CommitGenerate accurate conventional commit messages and intelligently stage files directly from natural language requests.40.6k37.2k
Resolve Merge ConflictsQuickly understand and resolve Git merge conflicts without losing context or breaking changes.16.5k148FAQ
What commit types does this skill use?
feat, fix, docs, style, refactor, perf, test, chore, and revert.
What are the length limits?
The subject must be 50 characters or fewer and each body line 72 characters or fewer.