Commit Work

A structured workflow for turning messy git state into reviewable commits. It walks you through inspecting diffs, deciding commit boundaries (feature vs refactor, backend vs frontend), using patch staging for mixed changes, and writing Conventional Commits with proper what-and-why messages. The checklist enforces the boring parts people skip: reviewing staged changes with git diff --cached, running a quick verification pass, and actually splitting work instead of dumping everything into one commit. Useful when you've been heads-down coding and need to package the work for review, or when you want to stop writing "fix stuff" commit messages. It defaults to multiple small commits, which is the right bias.

skills.sh installs: 290
GitHub stars: 33.2K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add davila7/claude-code-templates --skill commit-work --agent claude-code

Installs 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.

SKILL.md on GitHub

Sponsors

Promote your product hereReach 125k+ visitors monthly Promote your product hereReach 125k+ visitors monthly