
Commit Work
This walks you through the full commit hygiene routine: inspect what changed, decide where to split, stage intentionally with patch mode, review the diff before committing, then write Conventional Commits messages that explain what and why. It's built for the moment when you've been heads-down coding and realize your working tree is a mess of formatting tweaks, bug fixes, and half a feature. The checklist enforces the staging review loop most of us skip, and it won't let you write a commit message until you can describe the change in one sentence. If you treat commits as checkpoints instead of documentation, this will slow you down in a good way.
- skills.sh installs
- 4.2K
- GitHub stars
- 2.7K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add softaworks/agent-toolkit --skill commit-work --agent claude-codeInstalls into .claude/skills of the current project.
Files
Commit work
Goal
Make commits that are easy to review and safe to ship:
- only intended changes are included
- commits are logically scoped (split when needed)
- commit messages describe what changed and why
Inputs to ask for (if missing)
- Single commit or multiple commits? (If unsure: default to multiple small commits when there are unrelated changes.)
- Commit style: Conventional Commits are required.
- Any rules: max subject length, required scopes.
Sponsors
Details
- Repository
- github.com/softaworks/agent-toolkit
- Categories
- Git & Pull Requests, Code Review & Quality, AI & Agent Building
More from softaworks/agent-toolkit
All 43- React Dev4.2K
- Marp Slide4.2K
- React Useeffect4.1K
- Codex4.1K
- Professional Communication4.1K
- Command Creator4.1K
- Dependency Updater4.1K
- Meme Factory4K
- Reducing Entropy4K
- Ship Learn Next4K
- Gemini4K
- Openapi To Typescript4K
- Feedback Mastery4K
- Difficult Workplace Conversations4K
- Domain Name Brainstormer4K
- Daily Meeting Update4K
- Game Changing Features4K
- Plugin Forge4K
- Naming Analyzer3.9K
- Lesson Learned3K
- Gepetto1.6K
- Requirements Clarity1K
- Jira854
- Draw Io838