group-commit

Group changed files into logical, atomic commits with conventional formatting.

Updated Jan 18, 2026
One-click install
npx skills add https://github.com/seanmars/ai-coding-setup --skill group-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: group-commit
Source: https://github.com/seanmars/ai-coding-setup/tree/main/ai/skills/group-commit
Command: npx skills add https://github.com/seanmars/ai-coding-setup --skill group-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Group changed files into logical, atomic commits.

Core Features & Use Cases

  • Split changes by feature or intent to keep history readable
  • Guarantee atomic commits for individual concerns
  • Enforce a plan-driven workflow with deterministic grouping

Quick Start

Use the skill to analyze your working tree and create a plan that splits changes into focused commits.

Frequently Asked Questions about group-commit

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

FAQPage Schema
How do I group related files into atomic git commits?

Atomic commits isolate individual concerns so each commit represents a single logical change, keeping version control history readable and making it easier to track or revert specific features independently.

How do I split a git working tree by feature intent?

The skill enforces conventional commit formatting with dependency-aware ordering, ensuring that grouped changes follow a deterministic sequence and standard commit message structure for version control consistency.

When do I need to split commits by intent in version control?

You need to split commits by intent in version control when multiple features or concerns are touched simultaneously, ensuring that grouped changes remain focused and your project history stays clean and readable.

What is the best way to manage multiple feature changes in a single git working tree?

The best way to manage multiple feature changes in a single git working tree is to apply a plan-driven workflow that analyzes the changes and deterministically groups them into separate, atomic commits based on their logical intent.