← All workflow demos

Turn mixed changes into clear commits.

Workflow film · 1:47

Turn mixed changes into clear commits.

Full instructions →

Real app recording · Original AI voice and presenter portrait · Captions included · Cuts and playback speed shown in the film. Narration uses Code Overlord’s theatrical English.

Read the transcript

One tangle. Three worthy chronicles. Here in the real Code Overlord agent terminal, I ask for a commit plan before anything is staged. The working tree contains an empty-result fix, saved-search persistence, their tests, and an independent documentation update. The agent must inspect the actual diff and preserve every existing change. This is a demonstration repository; waiting between stages has been cut.

The agent proposes three groups from the actual changes. The filter fix stays with its six regression tests. Saved-search persistence stays with its seven application tests. The local-data documentation gets its own commit. These changes separate cleanly by file. When changes overlap inside a file, ask the agent to show and separate the relevant hunks before approving.

I approve those exact groups directly in the same terminal. The instruction names the order, keeps reports and local configuration outside the commits, and asks for the checks, commit contents, and a comparison with the reviewed working tree. The agent now performs the agreed Git operations.

Here are the three actual commit identifiers and the files in each commit. All sixteen tests pass. The file hashes confirm that the five committed files still match the contents we reviewed, and the remaining local files stay outside the commits. Nothing was pushed. A clear plan, an explicit instruction, and a result you can inspect: a fitting end to the tangle.

Ask an agent to group a mixed diff into meaningful commits, then inspect what belongs in each.

Try this workflow yourself

Let editing agents reach a review point, then enter the instruction directly into the agent terminal in the intended repository.

Inspect the current Git changes and propose coherent feature commits. Keep the saved-view fix with its regression tests and separate the independent documentation update. Explain any changes that share a file. After I approve the plan in this terminal, stage only the intended files or hunks for each group, create the commits and show git log plus the contents of every commit. Verify that no change was lost. Do not push.

The agent proposes and performs ordinary Git operations through its terminal tools. Review overlapping hunks and check each commit against the starting diff. A commit belongs to one repository; publishing is a separate action.