Commit
- 6 installs
- 5 repo stars
- Updated August 5, 2026
- bjornmelin/dev-skills
commit is a skill that stages and commits changes in semantic, reviewable groups with scoped conventional messages.
About
commit stages and commits changes in semantic, reviewable groups. A developer uses it to organize commits or clean up a branch before pushing. It scopes to files from the current task, keeps each staged set to one semantic change, writes short conventional commit messages, and asks before staging unrelated or ambiguous changes.
- Stages and commits changes in semantic, reviewable groups instead of git add .
- Writes short scoped conventional commit messages ordered feat, fix, test, docs, refactor, chore
- Leaves unrelated dirty files alone and asks before staging ambiguous changes
Commit by the numbers
- 6 all-time installs (skills.sh)
- Ranked #466 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
commit capabilities & compatibility
- Capabilities
- git commit · conventional commits · branch cleanup
- Works with
- github
- Use cases
- code review
What commit says it does
Stage by purpose, not `git add .`, unless whole task one coherent change.
Default one scoped conventional commit when task cohesive. Split only for clearly separate semantic groups. Optimize for reviewability.
Multiple commits: prefer order `feat`, `fix`, `test`, `docs`, `refactor`, `chore`.
npx skills add https://github.com/bjornmelin/dev-skills --skill commitAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 6 |
|---|---|
| repo stars | ★ 5 |
| Last updated | August 5, 2026 |
| Repository | bjornmelin/dev-skills ↗ |
What it does
Stage and commit changes in semantic, reviewable groups with scoped conventional messages.
Who is it for?
Organizing a dirty working tree into clean, reviewable conventional commits before pushing.
Skip if: Blindly committing a whole tree with git add . when changes span unrelated concerns.
When should I use this skill?
A developer wants to commit changes, organize commits, or clean up a branch before pushing.
What you get
Changes split into minimal, reviewable conventional commits scoped to one semantic change each.
- scoped conventional commits
- reviewable commit groups
By the numbers
- 10-step commit workflow
Files
1. git status --short first; scope to files from current task or explicit user request. 2. Leave unrelated dirty files alone unless user explicitly asks for a whole-tree commit. 3. Mixed tree: inspect diffs before staging; keep staged set one semantic change. 4. Stage by purpose, not git add ., unless whole task one coherent change. 5. Default one scoped conventional commit when task cohesive. Split only for clearly separate semantic groups. Optimize for reviewability. 6. Multiple commits: prefer order feat, fix, test, docs, refactor, chore. 7. Short scoped conventional messages; match what changed. 8. Each commit minimal, reviewable, one change type. 9. Between groups: git status -sb; confirm next commit has only intended files. 10. Ask before staging unrelated user changes, unfamiliar generated churn, or ambiguous dirty tree that makes ownership ambiguous.
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
Does it use git add .?
No. It stages by purpose, not git add ., unless the whole task is one coherent change.
How are multiple commits ordered?
It prefers the order feat, fix, test, docs, refactor, chore.