commit-all

Group dirty git worktree changes into semantically coherent commits.

1|Updated Jan 29, 2015
One-click install
npx skills add https://github.com/hayamiz/catscope --skill commit-all-hayamiz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-all
Source: https://github.com/hayamiz/catscope/tree/main/.claude/skills/commit-all
Command: npx skills add https://github.com/hayamiz/catscope --skill commit-all-hayamiz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stacks and groups dirty changes in the working tree into meaningful, semantically coherent commits, reducing noise and improving history clarity.

Core Features & Use Cases

  • Inventory dirty files with git status --porcelain to reveal what changed
  • Automatically classify changes into logical commit groups by feature or task
  • Exclude temporary and scratch files by default, with an option to include them
  • Generate clean, descriptive commit messages tailored to each group

Quick Start

Group your current changes into focused commits with descriptive messages.

Frequently Asked Questions about commit-all

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

FAQPage Schema
How do I group dirty changes in a git worktree into coherent commits?

To group dirty changes into coherent commits, a tool inventories modified files via git status porcelain and automatically classifies them into logical commit groups by feature or task, generating descriptive commit messages for each group.

What is the best way to automatically split working tree changes into focused git commits?

Automatically splitting working tree changes into focused git commits involves classifying dirty files into semantic groups based on their feature or task, which reduces noise and improves version control history clarity without manual staging.

Can I exclude temporary and scratch files when grouping changes for git commits?

Yes, you can exclude temporary and scratch files when grouping changes for git commits by default, with an option to include untracked files using the --include-untracked argument when you need them in the commit history.

Does the commit grouping process support a dry run before staging changes?

Yes, the commit grouping process supports a dry run via the --dry-run argument, allowing you to preview how dirty changes in your local development worktree will be classified into semantic commits before actually staging them.

When do I need to group dirty files into semantic commits during local development?

You need to group dirty files into semantic commits during local development worktrees when performing feature work, bug fixes, or refactors, ensuring staged and meaningful version control updates that improve history clarity.