Writing git commits
Skill narumiruna/skills/skills/workflow-repository/writing-git-commits
npx -y skills add narumiruna/skills --skill writing-git-commitsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 8 stars8 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
Inspect local Git changes, draft or validate Conventional Commit messages, choose types/scopes, explain breaking changes, or create a focused commit from the actual selected diff.
SKILL.md
1.7 KB, as published. Nobody here has run it
Writing Git Commits
Inspect the selected diff before describing it. Draft, validate, or create a commit only to the extent requested.
Workflow
- Run
git status --short. For a requested commit, inspectgit diff --cachedfirst and unstaged changes when they affect the boundary. - Define one coherent intent. If selected changes contain unrelated work, propose separate commits instead of a vague combined message.
- Choose a lowercase Conventional Commits type from behavior and add a short noun-like scope only when it adds signal.
- Write
<type>[optional scope][!]: <description>with a specific diff-grounded description. - Add a body only for material why, constraints, or tradeoffs; add footers only for actual references or
BREAKING CHANGE:information. - When committing, stage only intended paths, re-inspect the index, create no empty commit, and verify the resulting commit and worktree state.
Use feat for new capability, fix for incorrect behavior, refactor for behavior-preserving structure, and docs for documentation-only changes. Prefer no scope, body, or footer unless it improves meaning.
Do not describe unstaged work, future plans, or unrelated cleanup. Follow repository-level Git and attribution rules rather than duplicating them here.
Read references/conventional-commits.md when type selection is ambiguous or exact breaking-change/footer syntax matters. Report the selected boundary and final message; if a commit was created, include its ID and remaining local changes.