auto-grouped-commit

Analyzes uncommitted git changes and groups them into logical commits with messages.

Updated May 20, 2026
One-click install
npx skills add https://github.com/TeXmeijin/agent-skills --skill auto-grouped-commit-texmeijin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-grouped-commit
Source: https://github.com/TeXmeijin/agent-skills/tree/main/.apm/skills/auto-grouped-commit
Command: npx skills add https://github.com/TeXmeijin/agent-skills --skill auto-grouped-commit-texmeijin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After long working sessions, developers often accumulate many uncommitted changes across unrelated tasks and lose track of what they did. This Skill reads every modified, staged, and untracked file, infers the intent behind the changes, and proposes or executes a clean commit split with appropriate messages. ## Core Features & Use Cases - Full change analysis: Reads the complete content of all changed files (not just diffs) to infer the purpose of each change and classify it by type (feat, fix, refactor, config, docs, etc.). - Commit split proposals: Presents recommended groupings with commit messages that follow the repository's existing style, plus verification steps and test suggestions. - Two modes: auto mode stages and commits the recommended plan directly; manual mode stops at analysis and proposals without touching git. - Use Case: You spent an afternoon tweaking dotfiles, adding a shell function, and updating configs without committing. Invoke the Skill to get a 3-commit split with messages, verification checklist, and automatic execution. ## Quick Start Ask the agent to analyze my uncommitted changes and split them into logical commits.

Frequently Asked Questions about auto-grouped-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I split uncommitted changes into multiple git commits?

Run the Skill in auto mode to have it read all changed files, infer the intent of each change, and group them into logical commits. It stages and commits each group sequentially with messages matching your repository's existing style.

How to analyze what changed in my working tree before committing?

The Skill runs git status, git diff, and git log in parallel, then reads the full content of every modified and untracked file. It summarizes the purpose of the work and classifies each change as feat, fix, refactor, config, docs, and similar categories.

Can I get commit suggestions without actually committing?

Yes, use manual mode by saying 'manual mode', 'proposals only', or 'do not commit'. The Skill stops after presenting the commit split plan, message candidates, verification steps, and test ideas without running git add or git commit.

Does it follow my repository's commit message convention?

Yes, it inspects the last 10 commits via git log to detect prefix usage, language, and length conventions, then matches that style. If no style is detectable, it falls back to a type: scope: summary format.

When does auto mode ask for confirmation before committing?

Auto mode pauses for confirmation when there are over 20 changed files, when change intent is ambiguous, when files may contain secrets or generated artifacts, or when destructive operations like git reset are required.