Claude Code SkillProductivity8 installs

Commit Work

"Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits."

Install with the Claude Code Templates CLI
$ npx claude-code-templates@latest --skill="productivity/commit-work" --yes

Requires Claude Code. The command adds this skill to your project's .claudedirectory — nothing runs on ToolZip's servers.

What's inside this skill

Component source

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.

Workflow (checklist)

1) Inspect the working tree before staging

- git status

- git diff (unstaged)

- If many changes: git diff --stat

2) Decide commit boundaries (split if needed)

- Split by: feature vs refactor, backend vs frontend, formatting vs logic, tests vs prod code, dependency bumps vs behavior changes.

- If changes are mixed in one file, plan to use patch staging.

3) Stage only what belongs in the next commit

- Prefer patch staging for mixed changes: git add -p

- To unstage a hunk/file: git restore --staged -p or git restore --staged <path>

4) Review what will actually be committed

- git diff --cached

- Sanity checks:

- no secrets or tokens

- no accidental debug logging

- no unrelated formatting churn

5) Describe the staged change in 1-2 sentences (before writing the message)

- "What changed?" + "Why?"

- If you cannot describe it cleanly, the commit is probably too big or mixed; go back to step 2.

6) Write the commit message

- Use Conventional Commits (required):

- type(scope): short summary

- blank line

- body (what/why, not implementation diary)

- footer (BREAKING CHANGE) if needed

- Prefer an editor for multi-line messages: git commit -v

- Use references/commit-message-template.md if helpful.

7) Run the smallest relevant verification

- Run the repo's fastest meaningful check (unit tests, lint, or build) before moving on.

8) Repeat for the next commit until the working tree is clean

Deliverable

Provide:

  • the final commit message(s)
  • a short summary per commit (what/why)
  • the commands used to stage/review (at minimum: git diff --cached, plus any tests run)
Type
Skill
Category
Productivity
Installs
8
Source
GitHub ↗

Related Claude Code Skills

SkillProductivity

File Organizer

Intelligently organizes files and folders by understanding context, finding duplicates, and suggesting better organizational structures. Use when user wants to clean up directories, organize downloads, remove duplicates, or restructure projects.

502 installsView →
SkillProductivity

Humanizer

|

104 installsView →
SkillProductivity

Brainstorming

"You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation."

48 installsView →
SkillProductivity

Invoice Organizer

Automatically organizes invoices and receipts for tax preparation by reading messy files, extracting key information, renaming them consistently, and sorting them into logical folders. Turns hours of manual bookkeeping into minutes of automated organization.

41 installsView →
SkillProductivity

Game Changing Features

Find 10x product opportunities and high-leverage improvements. Use when user wants strategic product thinking, mentions '10x', wants to find high-impact features, or says 'what would make this 10x better', 'product strategy', or 'what should we build next'.

29 installsView →
SkillProductivity

Notebooklm

Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth. Drastically reduced hallucinations through document-only responses.

29 installsView →

Catalog data and component content are sourced from the open-source davila7/claude-code-templates project (MIT license). ToolZip curates the listing and writes original descriptions; every component links back to its original source. Claude Code is a product of Anthropic. ToolZip is an independent catalog and is not affiliated with or endorsed by Anthropic.