Partition pending changes into atomic Conventional Commits with git add -p.
npx skills add https://github.com/mhert/claude-code-helpers --skill git-commit-mhert
Please help me install this Agent Skill. Skill: git-commit Source: https://github.com/mhert/claude-code-helpers/tree/main/skills/git-commit Command: npx skills add https://github.com/mhert/claude-code-helpers --skill git-commit-mhert
This Skill prevents messy, multi-concern commit history by automatically guiding you to split pending work into atomic chunks and write Conventional Commits messages that explain the motivation, not just the diff.
Use the git-commit skill to stage and commit your current working changes as multiple atomic commits with Conventional Commits messages that explain the why.
High-intent search queries and answers about installing and using this skill.
To split pending git changes into atomic commits, you group related diff hunks into individual logical changes and stage them precisely using git add -p, ensuring each commit represents a single reviewable unit.
A conventional commit message uses a structured type, scope, and subject format to categorize changes. It focuses on explaining the motivation behind the diff in the body, rather than just describing what was changed.
You stage specific hunks without adding entire files by using precision staging techniques like git add -p. This allows you to interactively select individual diff sections that belong to a single logical commit.
Yes, you can amend commits on an owned feature branch. The process applies to creating and amending commit history by validating that each commit accurately reflects only the staged hunks.
The best way to generate git commit messages for refactoring is to partition pending changes by type and scope, drafting conventional messages with a subject, body, and optional breaking-change footers that match the staged hunks.
alexherreroScan git diffs and working trees for PII before commits or pushes.
dtbuchholzStage Git changes, create conventional commits, push branches, and open pull requests via GitHub CLI.
muhammadhamad1104Automate repository shipping workflows with branch operations, tests, and pull requests.
OiAnthonyGenerate conventional git commit messages from repository changes.
