commit-organizer

Analyze uncommitted git changes and propose logical commits with clear messages.

6|1|Updated Jan 22, 2026

Search Tags:#git #workflow #commits #organization #messages #analyze #version-control

Ready to run

npx skills add https://github.com/tryhuset/agent-skills --skill commit-organizer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-organizer
Source: https://github.com/tryhuset/agent-skills/tree/main/skills/commit-organizer
Command: npx skills add https://github.com/tryhuset/agent-skills --skill commit-organizer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze uncommitted changes in the repository and transform them into a set of logical, well-described commits with precise messages.

Core Features & Use Cases

Groups changes by type (features, fixes, refactors, docs) to form cohesive commits.
Generates clear, imperative commit messages that follow project conventions.
Provides a safe workflow that preserves the ability to revert or cherry-pick changes.

Quick Start

Analyze the current git state and generate a sequence of logical commits with concise, actionable messages.

Frequently Asked Questions about commit-organizer

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

FAQPage Schema

How do I organize uncommitted git changes into logical commits?▼

To organize uncommitted git changes into logical commits, you can analyze the current repository state to group edits by category such as features, fixes, docs, and refactors. This generates a sequence of cohesive commits with clear messages.

What is the best way to generate clear commit messages for multiple unrelated edits?▼

The best way to generate clear commit messages for unrelated edits is to group changes by type and follow project conventions. This approach analyzes the uncommitted changes and creates precise, imperative messages for each logical commit.

Can I group changes by category before pushing to version control?▼

Yes, you can group changes by category before pushing to version control. The process categorizes uncommitted edits into features, fixes, docs, and refactors to form cohesive commits that enforce a sensible commit order and a clean history.

Does organizing commits this way preserve my ability to revert or cherry-pick changes?▼

Organizing commits this way does preserve your ability to revert or cherry-pick changes. The workflow provides a safe sequence of logical commits that maintains full version-control flexibility for future adjustments.

How do I enforce a sensible commit order when I have mixed feature and fix edits?▼

To enforce a sensible commit order with mixed feature and fix edits, analyze the uncommitted changes and group them by category. This ensures features, fixes, refactors, and docs are separated into a logical sequence with guideline-driven messages.

When do I need to analyze uncommitted changes for a clean git history?▼

You need to analyze uncommitted changes for a clean git history when your session involves multiple unrelated edits. This process transforms scattered changes into well-described commits before you push to your repository.