skills.rest
brandon-fryslie
brandon-fryslieCOMMUNITY
Explore all skills by this author →
GitHub

organize-commits

Review and organize uncommitted Git changes into logical commits.

4|Updated Jan 12, 2017
Search Tags:#code quality#code review#Git#commit management#commit organization
One-click install
npx skills add https://github.com/brandon-fryslie/dotfiles --skill organize-commits-brandon-fryslie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: organize-commits
Source: https://github.com/brandon-fryslie/dotfiles/tree/main/config/claude/skills/organize-commits
Command: npx skills add https://github.com/brandon-fryslie/dotfiles --skill organize-commits-brandon-fryslie

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps developers manage a dirty working tree by reviewing and organizing uncommitted changes into logical commits, ensuring a clean and coherent codebase.

Core Features & Use Cases

  • Review and Organize: Analyze and group uncommitted changes by concern, not by file count.
  • Problem Surfacing: Identify and report issues like debug leftovers, secrets, conflicting edits, and rule violations.
  • Commit Execution: Execute each commit as a focused unit, ensuring no unintended changes are committed.
  • Use Case: When you have multiple logical changes in your working tree and want to ensure they are reviewed and committed properly.

Quick Start

Organize your commits by running the 'organize into commits' command.

Frequently Asked Questions about organize-commits

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, this Skill analyzes your dirty working tree and groups changes by concern, executing each group as a focused, logical commit to ensure a coherent codebase.

Can I check for debug leftovers and secrets before committing?▼

Yes, you can check for debug leftovers and secrets before committing. This Skill surfaces issues like debug code, committed secrets, conflicting edits, and rule violations during the commit organization process.

What is the best way to split multiple file changes into focused Git commits?▼

The best way to split multiple file changes into focused commits is grouping them by logical concern rather than file count. This Skill reviews uncommitted changes and executes each logical unit as a separate commit.

Do I need a clean working tree to review and organize commits?▼

No, you do not need a clean working tree to start, but this Skill requires a Git repository with configured hooks and conventions. It reviews your uncommitted changes and executes commits to achieve a clean state.

Why does commit organization group changes by concern instead of by file?▼

Commit organization groups changes by concern to ensure each commit represents a single logical modification. This prevents unintended changes from being committed together and maintains a clean, coherent project history.

Related Skills

Explore More Software Engineering Skills→
borkwebborkweb
7

commit-writer

Generate conventional git commit messages from staged diffs and repository history.

Community
Intermediate
gralwebgralweb

create-pr

Generate GitHub pull requests from branch commits using GitHub CLI.

Community
Advanced
alexmondalexmond
4

precommit

Automate Maven pre-commit checks for formatting, static analysis, and tests.

Community
Intermediate
rcdaileyrcdailey
1

git-hunks

Stage specific Git hunks by stable ID for atomic commits.

Community
Intermediate