mcpbeat Sign in

Commit Work Agent Skill

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.

2k tokens
context cost
the whole folder, loaded on every use
3
files
instructions only
2
copies elsewhere
how many repositories repackaged it
2271
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/softaworks/agent-toolkit --skill commit-work

The instruction itself

5 sections, as written by the author

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)

Other skills for the same job

different authors, same section of the catalogue
Git Commit
by github
vendor ×3

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

799 tokens
Github Code Review
by ComeOnOliver
×3

Comprehensive GitHub code review with AI-powered swarm coordination

13k tokens
Verification & Quality Assurance
by Microck
×2

Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.

4k tokens
Gh CLI
by christophacham
×2

GitHub CLI (gh) comprehensive reference for repositories, issues, pull requests, Actions, projects, releases, gists, codespaces, organizations, extensions, and all GitHub operations from the command line.

10k tokens
Github
by Dicklesworthstone
×2

GitHub CLI - manage repositories, issues, pull requests, actions, releases, and more from the command line.

1k tokens
Codebase Cleanup Refactor Clean
by ComeOnOliver
×2

You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.

9k tokens
Codebase Cleanup Tech Debt
by ComeOnOliver
×2

You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti

6k tokens
Legacy Modernizer
by ComeOnOliver
×2

Refactor legacy codebases, migrate outdated frameworks, and implement gradual modernization. Handles technical debt, dependency updates, and backward compatibility. Use PROACTIVELY for legacy system updates, framework migrations, or technical debt reduction.

3k tokens

How to use it

Copy the folder

Take softaworks/commit-work from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.