commit-all-the-things

Groups all uncommitted git changes into logical commits with descriptive messages.

4|Updated Jun 9, 2026

Search Tags:#git #workflow #version control #commit #cleanup #staging #diff

Ready to run

npx skills add https://github.com/laicluse/agent-fieldkit --skill commit-all-the-things-laicluse

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-all-the-things
Source: https://github.com/laicluse/agent-fieldkit/tree/main/.agents/plugins/generated/git-discipline/skills/commit-all-the-things
Command: npx skills add https://github.com/laicluse/agent-fieldkit --skill commit-all-the-things-laicluse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? A working tree cluttered with changes from multiple sessions is hard to commit cleanly. This Skill reads every diff, groups related changes into coherent stories, and produces a sequence of small, well-scoped commits until the tree is clean. ## Core Features & Use Cases - Logical grouping: Reads diffs (not just file names) to identify which changes belong to the same story, such as a script plus its configuration entry. - Hunk-level staging: Uses `git add -p` to split a single file across multiple commits when its hunks belong to different stories. - Ordered commits: Commits deletions and cleanup first, then config, features, and documentation. - Use Case: After a long day of mixed edits across hooks, skills, and docs, invoke the skill and get a clean history of small commits without sorting anything yourself. ## Quick Start Ask the agent to commit all uncommitted changes in the repository, grouped into logical commits.

Frequently Asked Questions about commit-all-the-things

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

FAQPage Schema

How do I commit all uncommitted git changes in logical groups?▼

Invoke the skill and it reads every diff, groups related changes into coherent stories, stages them with explicit paths or git add -p, and commits each group separately. It repeats until the working tree is clean, then reports a table of commit hashes and messages.

How to split changes in one file across multiple git commits?▼

Use git add -p to stage only the hunks belonging to the current story, leaving other hunks for later commits. The skill verifies each staging with git diff --cached --stat before committing.

Does this skill push commits to the remote repository?▼

No, the skill only creates local commits and never pushes. Pushing is treated as a separate action that the user triggers explicitly after reviewing the commit history.

When should I not use bulk commit grouping?▼

Avoid it when you only want to commit the current session's work, since this skill commits everything in the tree. It is also unsuitable when changes require individual review before any commit is created.

Why does the skill avoid git add -A or git add .?▼

Blanket staging mixes unrelated changes into one commit, defeating logical grouping. The skill always stages explicit paths or individual hunks so each commit tells one coherent story.