Group uncommitted Git changes into atomic commits with conventional messages.
npx skills add https://github.com/ameyalambat128/dotfiles --skill commit-chunks
Please help me install this Agent Skill. Skill: commit-chunks Source: https://github.com/ameyalambat128/dotfiles/tree/main/claude/skills/commit-chunks Command: npx skills add https://github.com/ameyalambat128/dotfiles --skill commit-chunks
This Skill helps you break large sets of uncommitted changes into small, logical, atomic commits, reducing risk and improving history readability.
Run this workflow on your repository to review uncommitted changes, group them into commits, stage files selectively, and commit with clear messages. For example, start with git status and git diff, then create one commit per logical change and push to your branch.
High-intent search queries and answers about installing and using this skill.
Atomic commits group related changes into single, purposeful commits. Use git status and git diff to review your changes, then stage related files with git add and commit each group with a conventional message (feat, fix, chore, docs, refactor, style). This reduces risk and improves history readability across feature work, bug fixes, refactors, and documentation updates.
Use conventional commit format with a type prefix—feat, fix, chore, docs, refactor, or style—followed by a clear, concise description of what changed and why. Each commit should represent one logical change, making your Git history scannable and easier to bisect or revert.
This Skill identifies uncommitted changes across multiple files and groups them into meaningful, atomic commits by staging relevant files selectively and applying conventional commit messages. You review the changes, decide logical groupings, then the workflow handles staging and committing with a final summary via git log.
Atomic commits are essential when you have edits spanning multiple files for different purposes—feature additions, bug fixes, refactors, or chores. Each logical unit in its own commit makes code review clearer, enables precise git bisect searches, and lets you revert individual changes without affecting unrelated work.
Yes, this Skill applies to local Git repositories with uncommitted edits. It's designed for feature branches, bug fixes, refactors, chores, and documentation updates on any repository where you have unstaged changes across one or more files.
After staging and committing each logical group with conventional messages, the workflow displays a summary using git log --oneline -10, showing your latest commits. You can then review the changes, verify they're correct, and push to your branch.
ebknStage and commit changes with conventional messages and logical grouping.
sumrae412Automate conventional commits, pull requests, and 10-step code review before merging.
wincentCreate Conventional Commits for Git and Jujutsu repositories.
MuvonStandardize Git commit messages, branch names, and history workflows.
