autoresearch-finalize

Convert autoresearch sessions into independent branches from the merge-base.

6|1|Updated Nov 23, 2023
One-click install
npx skills add https://github.com/gmcabrita/dotfiles --skill autoresearch-finalize-gmcabrita
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autoresearch-finalize
Source: https://github.com/gmcabrita/dotfiles/tree/main/.pi/agent/skills/autoresearch-finalize
Command: npx skills add https://github.com/gmcabrita/dotfiles --skill autoresearch-finalize-gmcabrita

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node.

What problem does it solve?

Finalizes an autoresearch session into clean, reviewable branches, making it easy to share, review, and merge experiments.

Core Features & Use Cases

  • Split autoresearch experiments into independent branches from the merge-base to enable parallel review and merging.
  • Validate group boundaries by ensuring no file is touched by more than one group and preview dependencies across groups.
  • Verify that the union of all group branches matches the original autoresearch branch, and provide a summary with cleanup guidance.

Quick Start

Run the finalize script with a groups.json describing your autoresearch session to generate independent branches from the merge-base.

Frequently Asked Questions about autoresearch-finalize

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I split git experiment branches into independent reviewable commits?

To split git experiment branches into independent reviewable commits, this Skill reads autoresearch.jsonl and autoresearch.md, expands short commits to full hashes, computes the merge-base with main, and creates a branch per kept commit for review and collaboration.

How do I convert autoresearch experiments into branches derived from the merge-base?

Converting autoresearch experiments into branches derived from the merge-base requires running a finalize script with a groups.json file, which generates independent branches from the merge-base to enable parallel review and merging.

Can I validate group boundaries when splitting branches to ensure no file overlaps?

Validating group boundaries when splitting branches is supported by checking that no file is touched by more than one group, while also previewing dependencies across groups to ensure clean separation.

Do I need Node.js to finalize autoresearch sessions into clean branches?

Node.js is a required dependency to finalize autoresearch sessions into clean branches, as the Skill relies on the Node runtime to execute its finalize script and process the git automation.

Why does the union of group branches need to match the original autoresearch branch?

Verifying that the union of all group branches matches the original autoresearch branch ensures no commits or file changes were lost during the split, providing a reliable summary with cleanup guidance for the review process.

What is the best way to prepare autoresearch data for branch splitting?

Preparing autoresearch data for branch splitting involves ensuring your autoresearch.jsonl and autoresearch.md files are available, then defining a groups.json configuration to describe your session boundaries for the finalize script.