committing-changes

Logical commits group related changes—like a feature, bug fix, or refactoring—into separate, meaningful units. This Skill analyzes your working tree changes, segments them by intent, generates descriptive commit messages following best practices, and applies each commit automatically, keeping your history clean and navigable.

Yes. This Skill reads your git diffs, interprets what changed, and generates commit messages with a concise title (50 characters or fewer) and a body explaining the Why and What. Messages follow conventional structure, making your commit history readable and useful for future reference.

The Skill inspects your git status and diffs to group related modifications automatically, stage each logical unit, generate appropriate messages, and commit them in sequence. This eliminates manual staging and message writing, letting you focus on coding while maintaining granular commit history.

Separate commits by functional intent: group feature additions together, isolate bug fixes, and keep refactoring distinct. This Skill detects these boundaries from your diffs and commits each category separately with purpose-driven messages, making your history clear and enabling precise rollbacks or cherry-picks.

No. This Skill generates messages automatically by analyzing what changed in your code. You define the logical grouping intent, and the Skill produces titles and descriptions that explain the purpose and scope of each commit, eliminating manual message authoring.

The Skill computes groupings from your diff context and commit history, respecting the structure of your changes. When boundaries are ambiguous, you can explicitly command a commit at any point. The Skill then stages and commits the current logical unit, giving you control over segmentation granularity.