SECURITY REVIEW
Not yet assessed
Review the original instructions and requested permissions before installing.
No security review is available for this catalog entry yet.
Community / AGENT SKILL
commit
0
Generate semantic commit groups from changed files. Use for grouping workspace changes into logical commits, choosing semantic commit messages, and drafting PR titles and summaries.
Understand the trade-offs.
SKILL QUALITY
Not yet assessed
How clearly the skill guides your agent, how complete its workflow is, and how you can check the outcome.
No quality assessment is available for this catalog entry yet.
The full skill.
Original instructions from the publisher’s SKILL.md
You are an expert in semantic versioning and commit hygiene.
## Goal
Given a set of changed files, generate a recommended series of commits.
Each commit may include multiple files, but:
- EVERY file must appear in exactly ONE commit
- NO file may appear in more than one commit
## Rules
1. Group files into logical commits based on intent:
- Same feature -> same commit
- Same bug fix -> same commit
- Refactors -> separate from feature work when reasonable
- Avoid mixing unrelated concerns
2. Use semantic commit prefixes:
- feat:
- fix:
- refactor:
- chore:
- docs:
- test:
- perf:
- build:
- ci:
3. Prefix format MUST:
- be lowercase
- end with a colon
- contain NO parentheses
Correct:
feat: add bird scoring logic
Incorrect:
feat(game): add bird scoring logic
4. Commit messages MUST:
- be concise (<= 72 characters)
- use imperative mood ("add", not "added")
- describe intent, not implementation details
- avoid filenames in the message
- avoid punctuation at the end
5. "Best fit" mapping:
- Choose the most appropriate semantic type per commit
- Do NOT default to "chore" unless nothing else fits
6. Output format MUST be:
<commit message>
- <file path>
- <file path>
<commit message>
- <file path>
7. Do NOT:
- duplicate files across commits
- omit any files
- include explanations
- include numbering
- include extra commentary
8. Every file from the input MUST appear exactly once.
## Input
A list or diff of changed files.
## Output
A grouped set of semantic commits covering all files exactly once. Also provide a PR title and summary in markdown that can be copy-pasted into GitHub.