commit-all

Groups staged Git changes into logical commits by intent with concise messages.

Updated Apr 14, 2026

Search Tags:#git #workflow #commit #code-quality #best-practices #version-control #change-management

Ready to run

npx skills add https://github.com/jrmatherly/spacebot --skill commit-all-jrmatherly

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-all
Source: https://github.com/jrmatherly/spacebot/tree/main/.claude/skills/commit-all
Command: npx skills add https://github.com/jrmatherly/spacebot --skill commit-all-jrmatherly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you avoid oversized, unclear commits by automatically grouping related changes into separate, informative commits, improving git history readability and traceability.

Core Features & Use Cases

Group changes by intent (bug fixes, features, refactors) and prepare them as separate commits.
Stage only files belonging to each group, preserving logical boundaries and dependencies.
Write concise commit messages that describe what changed and why, following the repository's established style.

Quick Start

Group all staged changes into logical commits by intent, review them, and push when ready.

Frequently Asked Questions about commit-all

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

FAQPage Schema

How do I group staged changes into logical commits with distinct intent?▼

To split oversized commits, stage only files belonging to each logical group across the working tree, ensuring each commit corresponds to a single reason like a bug fix or feature, then verify the tree is clean before committing.

What is the best way to improve git history clarity when committing multiple file changes?▼

Improving git history clarity requires grouping related changes into separate, informative commits based on their intent, preserving logical boundaries and dependencies, and verifying the tree is clean before finalizing the commits.

How does grouping changes by intent affect version control and change management?▼

Grouping changes by intent improves version control traceability by ensuring each commit represents a single reason for modification, which simplifies code reviews and makes repository history easier to read and revert.

Can I write concise commit messages that follow my repository's established style automatically?▼

Yes, the grouping process writes concise commit messages that describe what changed and why, following the repository's established style to maintain consistency across your version control history.

Why should I avoid oversized commits in my git workflow?▼

Oversized commits reduce git history readability and traceability by mixing unrelated changes, making it difficult to isolate specific bug fixes, features, or refactors during code reviews or issue resolution.