skills.rest
epologee
epologeeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

commit-all-the-things

Group git working tree changes into logical commits without pushing.

3|1|Updated Apr 4, 2026
Search Tags:#automation#git#workflow#commit#staging#diff
One-click install
npx skills add https://github.com/epologee/leclause-skills --skill commit-all-the-things
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-all-the-things
Source: https://github.com/epologee/leclause-skills/tree/main/packages/commit-all-the-things/skills/commit-all-the-things
Command: npx skills add https://github.com/epologee/leclause-skills --skill commit-all-the-things

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps developers quickly and reliably commit all remaining uncommitted changes in a git working tree by grouping related edits into logical, descriptive commits so the working tree is cleaned without manual, error-prone sorting.

Core Features & Use Cases

  • Logical grouping: Reads diffs and groups related hunks into single conceptual changes rather than committing by file.
  • Selective staging: Encourages use of interactive hunk staging to split files with mixed changes into multiple commits.
  • Opinionated ordering: Commits removals and cleanups first, then config, features, and documentation, producing a predictable history.
  • Non-destructive workflow: Commits locally only, never pushes, and reports resulting commit hashes and messages for traceability.

Quick Start

Run the command /commit-all-the-things to have the tool read diffs, stage coherent hunks, and create logical commits until the working tree is clean.

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 changes in git into logical commits?▼

To commit all uncommitted changes, the Skill reads git diffs, selectively stages related hunks, and groups them into logically descriptive commits until the working tree is clean. It avoids using git add -A and enforces one logical change per commit.

What is the best way to split mixed changes in a git working tree into separate commits?▼

The best way to split mixed changes is selective hunk staging, which groups related edits across files into single conceptual commits rather than committing by file. This approach ensures one logical change per commit without manual sorting.

Can I automatically group related git diffs without using git add -A?▼

Yes, you can automatically group related git diffs without git add -A. The Skill applies selective staging to group coherent hunks into individual commits, enforcing a predictable ordering of removals, config, features, and documentation.

Does committing all uncommitted changes push the local commits to a remote repository?▼

Committing all uncommitted changes operates non-destructively and never pushes to a remote repository. The workflow commits locally only, reporting each resulting commit hash and message for traceability.

When should I avoid using an automated git commit workflow?▼

You should avoid this automated git commit workflow if you need to push commits to a remote repository or require interactive manual control over every staging decision. It is designed for local, non-interactive complete cleanup of mixed changes.

Related Skills

Explore More Software Engineering Skills→
ian-pascoeian-pascoe
1

git-commit

Generate conventional git commit messages and stage related file changes.

Community
Advanced
gtpgg1013gtpgg1013

git-teacher-upload

Push local commits to a configured GitHub repository and report the resulting URL.

Community
Advanced
Juhwa-Lee1023Juhwa-Lee1023

git-master

Enforce atomic commits and descriptive messages in Git workflows.

Community
Basic
rcdaileyrcdailey
1

git-hunks

Stage specific Git hunks by stable ID for atomic commits.

Community
Intermediate