autoresearch-finalize

Splitting a Git commit tree into independent branches requires finalizing changesets from a common merge-base. This Skill automates branch creation from grouped logical changes, validating the union against the original experiment to ensure clean review.

Organizing experimental Git commits into reviewable changesets involves grouping related file-level changes into separate branches. This preserves order and dependencies while maintaining independence, reducing noise and improving collaboration during the review process.

Yes, finalizing an autoresearch session into separate branches requires a JSON file defining branch groups. You must also have a working Git environment and access to the relevant commit tree to execute the finalization command successfully.

Validating independent branches against an original commit tree confirms that the combined branches accurately reflect the original experiment changeset. This verification step ensures no file-level changes are lost during the branch separation process.

Yes, you can clean up branches after finalizing an autoresearch session. Upon successful completion and validation of the separated branches, the Skill provides specific cleanup instructions to remove temporary or intermediate artifacts from your Git environment.

Autoresearch branches may not be independent if logical changesets overlap at the file level. This Skill enforces branching from a common merge-base to ensure file-level independence, preserving related changes together for accurate collaborative review.