Branch Analysis & Insights FAQs

Question 1

What happens if there is no common ancestor between branches?

Accepted Answer

The skill will prompt you to choose an alternative: analyzing the entire branch history, specifying an iteration range manually, or providing a specific commit hash to use as the starting point.

Question 2

Does this skill change my current branch or files?

Accepted Answer

No. This skill performs read-only operations using commands like 'git show' and 'git ls-tree'. it never performs a checkout or modifies your current working directory.

Question 3

Can I use this to review my current branch progress?

Accepted Answer

No, this skill is specifically for analyzing other branches. To review progress on your current branch, you should use the /review-progress command instead.

Question 4

What is the Analyzing Branches skill used for?

Accepted Answer

It is used to extract lessons, decisions, and findings from a different Git branch's history, specifically looking at 'autonomy' iteration journals to summarize work that diverged from your current branch.

Question 5

Do I need specific files for this to work?

Accepted Answer

Yes, the skill requires the project to have an autonomy goal defined (autonomy/*/goal.md) and relies on iteration tags and journal files created by the autonomy plugin.

Branch Analysis & Insights

Key Features

Use Cases

Branch Analysis & Insights

Key Features

Use Cases