comparing-branches

Compare two autonomy branches and report divergence, iterations, metrics, and outcomes.

3|1|Updated Dec 12, 2025
One-click install
npx skills add https://github.com/tilmon-engineering/claude-skills --skill comparing-branches
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: comparing-branches
Source: https://github.com/tilmon-engineering/claude-skills/tree/main/plugins/autonomy/skills/comparing-branches
Command: npx skills add https://github.com/tilmon-engineering/claude-skills --skill comparing-branches

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users quickly identify and understand the divergences between two autonomy branches, showing how approaches, decisions, and outcomes differ.

Core Features & Use Cases

  • Deterministic comparison: Uses git merge-base to determine divergence and dispatches the branch-analyzer for computation.
  • Comprehensive report: Generates a structured markdown report covering divergence, iterations, metrics, decisions, and outcomes.
  • Non-destructive analysis: Reads commit history via git log without checking out or modifying any branches.

Quick Start

Use the compare-branches skill to compare two autonomy branches, e.g., autonomy/experiment-a and autonomy/experiment-b, with the /compare-branches command.

Frequently Asked Questions about comparing-branches

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

FAQPage Schema
How do I compare two git branches to find differences in metrics and outcomes?

You can compare two git branches by running a branch comparison command with two branch names. The analysis uses git history to generate a report covering divergence point, iteration counts, metrics, and status without modifying the repository.

What is the best way to see where two autonomous experiment branches diverged in git?

To see where branches diverged, use a branch-analyzer tool that applies git merge-base logic. This identifies the exact divergence point and computes a structured report of all differences between the two branches.

Can I compare autonomy branches without checking out or modifying my repository?

Yes, you can compare autonomy branches read-only. The analysis reads commit history directly via git log without checking out or modifying any branches, ensuring a non-destructive evaluation of your repository state.

How do I generate a report comparing iterations and decisions across two branches?

Generate a report comparing iterations and decisions by running a branch comparison command with two branch names. The resulting structured markdown report covers divergence, iteration counts, metrics, decisions, and outcomes.

Does branch comparison work with any git branch or only specific ones?

Branch comparison specifically applies to autonomy branches. It is designed to compare branches following the autonomy/* naming convention, analyzing divergence, iteration counts, metrics, and status between two specified branch names.

What git metrics are included when analyzing branch divergence?

When analyzing branch divergence, the generated report includes iteration counts, metrics, decisions, and outcomes. The computational analysis focuses on comparing these elements between two branches from their divergence point onward.