Git commit
Skill kimtth/agent-skill-100-lines-or-less/skills/git-commit
🧿 Minimal but effective AI agent skill definitions in 100 lines or less.
npx -y skills add kimtth/agent-skill-100-lines-or-less --skill git-commitAssembled 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.
- 2 stars2 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
Use when: create a conventional git commit from the current diff with logical staging and message analysis.
SKILL.md
1.1 KB, 225 tokens by cl100k_base, as published. Nobody here has run it
Goal: create one clear commit that matches the actual change.
Use for:
- "commit this", "write a commit message", or
/commit - grouping related file changes
- generating Conventional Commit messages from a diff
Workflow:
- Inspect
git status --shortand the relevant diff. - Separate unrelated user changes from this task's changes.
- Stage only the intended logical group.
- Choose type and optional scope from the diff.
- Write an imperative subject under 72 chars, ideally under 50.
- Add a body only when the reason is not obvious.
- Commit only after explicit user approval.
Types:
- feat, fix, refactor, perf, docs, test, chore, build, ci, style, revert
Message shape:
<type>(<scope>): <imperative summary>
<body only when useful>
Rules:
- do not stage unrelated changes
- do not include secrets or generated noise
- do not commit without the user's clear request
- mention tests or verification in the body only when relevant