git-commit-crafter_skill

Overview

This skill creates atomic, independently revertible git commits that follow the Conventional Commits specification. It analyses working changes, splits them into logical hunks, and crafts clear, well-structured messages to make history easy to review and revert. The skill favours small, focused commits over large aggregations and matches existing project commit patterns.

How this skill works

The skill surveys the working tree and diffs to identify self-contained revertible units of work. For each unit it produces a patch, applies it with git apply best practices, stages the resulting files and generates a Conventional Commits-compliant message with type, scope, body and footer. It verifies each commit and advises on troubleshooting failed patch applications and contextual adjustments.

When to use it

• Committing multiple unrelated changes in the same working tree
• Splitting large edits into safe, independently revertible commits
• Preparing commits that must match project commit patterns or CI checks
• Documenting rationale in commits for later code review or auditing
• Creating clean history before opening a pull request
• Applying patches produced by code generation or refactors

Best practices

• Prefer the smallest logical unit that can be reverted without breaking other features
• Match project's existing scope naming and message style by checking recent commits
• Always run git apply --check before applying a patch and use -v for feedback
• Use --whitespace=fix, --reject or --ignore-space-change when encountering whitespace or context mismatches
• Write body text explaining WHAT changed, WHY, implementation rationale and potential impacts; wrap at 72 characters
• Never push directly to main; create a PR and include issue/PR references when applicable

Example use cases

• Split a single file edit containing formatting, bugfix and feature work into three commits: chore(format), fix(...), feat(...)
• Commit an authentication refactor in separate steps: introduce service, integrate middleware, update tests
• Apply and commit hunks produced by an automated tool while keeping manual changes separate
• Prepare a series of descriptive commits before opening a release PR to make changelog generation trivial
• Resolve a complex merge by extracting each resolved hunk into its own small commit for easier review