commit-work_skill

Overview

This skill helps you create high-quality git commits by reviewing changes, staging only intended hunks, splitting unrelated work into logical commits, and writing clear Conventional Commit messages. It guides the commit process end-to-end so commits are easy to review and safe to ship. The skill returns final commit messages, short summaries, and the staging/review commands used.

How this skill works

Inspect the working tree and unstaged diffs to identify logical commit boundaries. Stage only the hunks that belong to the next commit (prefer patch staging) and review the index before committing. Compose Conventional Commit messages with a concise subject, optional scope, descriptive body explaining what and why, and any footers for breaking changes or references.

When to use it

• When you ask the agent to commit changes or craft commit messages.
• When a working tree contains mixed or unrelated changes and needs splitting.
• When you want Conventional Commits for CI, changelogs, or policy compliance.
• Before pushing to shared branches to ensure commits are reviewable and clean.
• When you need a reproducible sequence of small, verifiable commits.

Best practices

• Inspect unstaged and staged diffs first: git status, git diff, git diff --stat.
• Default to multiple small commits for unrelated changes; combine only truly cohesive changes.
• Use git add -p for mixed files and git restore --staged <path> to unstage mistakes.
• Describe the staged change in 1–2 sentences (what and why) before writing the message.
• Follow Conventional Commits: type(scope): short summary, blank line, body, footer.
• Run the fastest meaningful verification (unit tests or linter) after staging and before committing.

Example use cases

• Split a branch that contains formatting, a bugfix, and a dependency upgrade into three commits with clear messages.
• Stage only the bugfix hunks from several files using patch staging and commit with feat(parser): fix tokenization bug.
• Convert an ambiguous large change into multiple focused commits by grouping by purpose (tests, refactor, feature).
• Generate Conventional Commit messages for CI-driven changelog generation before a release.