Commit practices
Use when planning, reviewing, or writing git commits. Keep commits atomic and small, use English commit messages, describe concrete functionality, and follow Conventional Commits.From its SKILL.md
npx -y skills add gdebenedetti/skills --skill commit-practicesAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 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.
SKILL.md
1.4 KB, 271 tokens by cl100k_base, as published. Nobody here has run it
Commit Practices
Use this skill when preparing a commit or deciding whether a change should be split.
- One commit, one coherent change that can be reviewed and tested on its own.
- Split unrelated fixes, refactors, docs, and tests unless the test or doc change belongs directly to the same behavior change.
- Keep commits small. If the subject needs "and", it is probably two commits.
- Write commit messages in English.
- Use the Conventional Commits format:
<type>[optional scope]: <description>. - Prefer clear types such as
feat,fix,docs,refactor,test,chore,build,ci,perf,style, andrevert. - Write the description as a concise statement of concrete functionality or behavior. Prefer
feat(auth): add session timeout warningoverwip,more updates,address feedback, orcontinue work. - Use an optional body when the why or the impact is not obvious from the subject alone.
- Mark breaking changes explicitly with
!after the type or scope, and describe them in aBREAKING CHANGE:footer when relevant. - Before committing, check
git diff --stagedand confirm the staged change matches a single sentence and the chosen type still fits that sentence.
What ships with it: 1 file
187 B alongside SKILL.md
agents/
- openai.yaml187 B