About commit-work
commit-work is a repository skill for inspecting changes and preparing or creating Git commits. It follows git-conventions and provides guidance on staging, commit messages, checks, and reporting results.
Key features
- 01Inspect staged and unstaged changes
- 02Review recent commit history
- 03Format commit messages
- 04Recommend splitting unrelated changes
- 05Run checks before committing
Use cases
- 01Preparing a commit message
- 02Deciding which changes to stage
- 03Committing after requested checks
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ klausborges/ workflow-skills --skill commit-workAfter installing, type/commit-workin Claude Code to confirm it loaded.
Bundled filesagents/openai.yamlskill.toml
Details
From the project READMECommit Work
Message shape and style follow the git-conventions skill.
Workflow
- Inspect staged changes first:
git diff --staged --stat, then the diff itself. When nothing is staged, inspectgit status --shortand the working-tree diff, and name what you would stage. - Check
git log --oneline -10for scope and phrasing precedent. - Write the first line as
type(scope): description. Add a body only when the why is not obvious from the diff; wrap it near 90 columns and use repeated-mflags or--fileso paragraphs stay separate. - Recommend a split only when the diff contains clearly unrelated changes.
- Commit when the user asked for a commit; otherwise deliver the message and the staging suggestion.
Guardrails
- Stage files only when the user asks.
- Run the repo's fast checks before committing when they exist; let hooks run and report a failure instead of bypassing it.
- Describe the change itself; plan and milestone context stays out of the message.
Output
The commit SHA and first line, or the proposed message plus what to stage.
Comments
Markdown supported