commit-plan

To group dirty changes into logical commits without staging, this Skill performs a read-only analysis of your Git working tree to identify logical boundaries and produce a structured commit plan. It inspects changes across multiple files and branches without writing anything.

A safe commit plan is a structured release strategy generated by read-only analysis of your repository. It groups dirty changes into coherent commits, highlights dependencies, flags risky items like large binaries or secrets, and suggests safe alternatives without mutating files.

Yes, you can plan commits across multiple branches and files in one repository. The Skill applies to any Git workspace where changes are present, analyzing the working tree to propose coherent commit boundaries and structured release planning.

To identify risky items before committing, the Skill inspects your working tree and flags potential issues such as large binaries and secrets. It then suggests safe alternatives to help you avoid dangerous changes and improve reviewability.

The best way to review potential Git conflicts before staging is to use a read-only commit plan. It groups dirty changes into logical commits while highlighting dependencies and potential conflicts, allowing for structured release planning without altering your working tree.

No, the commit planning process does not modify or write changes to your files. It implements a strictly read-only analysis of the working tree to produce a commit plan, ensuring non-intrusive review without staging or committing any dirty changes.