git-commit-organizer

Organize uncommitted changes into descriptive commits by intent.

4|2|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/Formspec-org/formspec --skill git-commit-organizer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit-organizer
Source: https://github.com/Formspec-org/formspec/tree/main/.claude-plugin/skills/git-commit-organizer
Command: npx skills add https://github.com/Formspec-org/formspec --skill git-commit-organizer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organizes uncommitted work into logical, well-described commits by analyzing changes and grouping them by intent (feature, fix, refactor, docs, tests, chore), then guiding deliberate staging and messaging.

Core Features & Use Cases

  • Analyze diffs and cluster changes by intent (feature, fix, refactor, docs, tests, chore)
  • Stage whole files or individual hunks with deliberate control
  • Generate clear, conventional commit messages aligned with project style
  • Prepare branches for review or push with organized history

Quick Start

Inventory changes, plan commit buckets, and stage and commit each bucket with descriptive messages.

Frequently Asked Questions about git-commit-organizer

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

FAQPage Schema
How do I organize uncommitted git changes into clean commit messages?

To organize uncommitted git changes, the Skill inventories your work, clusters edits by intent, stages content precisely, and commits with purpose-driven descriptive messages.

What's the best way to group multiple file edits into separate logical commits?

Grouping multiple file edits into logical commits requires analyzing diffs to cluster changes by intent like feature, fix, refactor, docs, tests, and chore before staging each bucket.

Can I stage individual git hunks deliberately when preparing a clean version-control history?

Yes, you can stage individual git hunks deliberately. The workflow enforces precise staging control over whole files or specific hunks to prepare branches for review or push.

How do I generate conventional commit messages aligned with my project style?

Generating conventional commit messages aligned with project style happens automatically after the workflow clusters your uncommitted changes and plans deliberate commit buckets for each edit group.

Do I need any dependencies to organize messy work into described commits?

No dependencies are required. The Skill operates independently to inventory changes, plan commit buckets, and stage content precisely without needing external tools or additional environment setup.