Automatically organize unrelated changes into changelists

[stenci]

Describe the need of your request

During early development or prototyping, it's common to make multiple unrelated changes across different parts of the codebase. At commit time, reviewing and manually sorting these changes into separate changelists is time-consuming and error-prone, especially when the changes depend on each other and must be committed in a specific order.

This manual process slows down the workflow and increases cognitive load, particularly for solo developers who prefer fast, iterative work without the overhead of managing multiple branches.

Proposed solution

Introduce a command that analyzes local changes and automatically groups unrelated edits into separate changelists. The user can review, merge, or rearrange these changelists before committing, preserving full control over the process and commit order.

This feature would streamline the transition from exploratory coding to clean, structured commits, while maintaining flexibility and reducing the need for manual sorting.

Additional context

See similar FR in youtrack: https://youtrack.jetbrains.com/issue/LLM-2050

[stenci]

Alternative approach suggestion
Instead of relying entirely on automatic changelist generation—which can result in too many or too few groupings—consider an interactive workflow: start from a single change and build from there. The idea is to begin in the Local Changes window, inspect a diff, select a change, and trigger a ProxyAI - Create changelist command. At that point, I provide a commit-style description, and the plugin takes over.

With one concrete change and its description as a starting point, the plugin could more effectively find and group related edits. This reflects my current manual workflow: I start with a single change, create a changelist, then add related changes I remember or recognize. I repeat until all changes are grouped, sometimes rediscovering edits that belong in an earlier list.

This semi-automated approach gives me control over the number and purpose of changelists while also potentially being simpler to implement than full automation.