Group Git changes into logically ordered, buildable commits.
npx skills add https://github.com/webdevcody/go-mailing-list --skill commit-webdevcody
Please help me install this Agent Skill. Skill: commit Source: https://github.com/webdevcody/go-mailing-list/tree/main/.claude/skills/commit Command: npx skills add https://github.com/webdevcody/go-mailing-list --skill commit-webdevcody
This Skill helps you turn a sprawling working tree into a readable, reviewer-friendly commit history where each commit is logically related and buildable, instead of one mega-commit.
git status and cached diffs, then commits without skipping hooks.Tell the Skill to “commit these changes” and it will propose a multi-commit grouping, wait for approval, then apply the commits in an order that stays buildable.
High-intent search queries and answers about installing and using this skill.
You can split messy git changes by inventorying staged and unstaged files, grouping them by relatedness heuristics like test and implementation pairs, and applying safe per-group staged commits in a dependency-aware topological order.
Ordering commits for a bisectable history requires sorting groups topologically by dependencies, ensuring schema changes land before backend updates, which land before frontend consumers, maintaining buildability at every commit step.
Git bisect benefits from clean commits because splitting a sprawling working tree into dependency-aware, buildable commits ensures each step in the history compiles independently, allowing bisect to isolate exact failure points accurately.
Yes, you can commit refactors and feature slices separately without bypassing git hooks by staging only the exact paths per group, verifying with git status and cached diffs, and committing safely without skipping hooks.
Yes, this commit splitting approach works with both staged and unstaged file edits by performing a complete inventory of your working tree, analyzing diffs, and safely staging the exact paths needed for each logically grouped commit.
Heuristics used to group files when splitting a working tree include matching test and implementation pairs, rename and edit pairs, schema and reader coupling, and shared-module and first-consumer adjacency to form logical commit boundaries.
GLaDO8Generates concise Git commit messages and commits staged or unstaged changes.
vieitesssIdentify the exact commit that introduced a bug using git bisect.
roborev-devLaunch background design reviews for commits and present severity-grouped findings.
epologeeGroup git working tree changes into logical commits without pushing.