gpd-compare-branches

Compare hypothesis branches by extracting STATE.md, HYPOTHESIS.md, and SUMMARY data.

1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/CharlieGreenman/roomtemp-superconductor-gpd --skill gpd-compare-branches
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gpd-compare-branches
Source: https://github.com/CharlieGreenman/roomtemp-superconductor-gpd/tree/main/.agents/skills/gpd-compare-branches
Command: npx skills add https://github.com/CharlieGreenman/roomtemp-superconductor-gpd --skill gpd-compare-branches

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool helps researchers compare results across hypothesis branches by automating collection of STATE.md, HYPOTHESIS.md, SUMMARY.md, and VERIFICATION.md data, producing a clear, structured comparison that highlights agreements, discrepancies, and verification status.

Core Features & Use Cases

  • Build a comprehensive comparison table that includes a baseline parent branch and side-by-side metrics from all hypothesis branches.
  • Detect and highlight numerical disagreements, verification gaps, and context usage to guide decision-making.
  • Generate actionable guidance for merging winning branches back to the mainline, cleaning up obsolete branches, or exporting the comparison report for documentation.

Quick Start

Run the compare-branches workflow from the repository root to generate the branch comparison report.

Frequently Asked Questions about gpd-compare-branches

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

FAQPage Schema
How do I compare hypothesis branches side-by-side with verification status?

To compare hypothesis branches, the workflow extracts STATE.md, HYPOTHESIS.md, and SUMMARY data to build a baseline-inclusive side-by-side view, highlighting key verification status and numeric results for clear decision-making.

What is the best way to identify numerical disagreements across hypothesis branches?

Identifying numerical disagreements is handled by building a comprehensive comparison table that detects discrepancies, verification gaps, and context usage across all hypothesis branches alongside the baseline parent branch.

Can I get actionable guidance on merging winning branches back to the mainline?

Yes, actionable guidance for merging winning branches back to the mainline is generated automatically, alongside recommendations for cleaning up obsolete branches or exporting the comparison report for documentation.

How do I generate a branch comparison report from the repository root?

Generating a branch comparison report requires running the compare-branches workflow from the repository root, which automates collection of STATE.md, HYPOTHESIS.md, SUMMARY.md, and VERIFICATION.md data into a structured output.

Does the branch comparison include the baseline parent branch metrics?

Yes, the branch comparison includes the baseline parent branch metrics by building a baseline-inclusive, side-by-side view that aggregates results and verification data from all hypothesis branches for comprehensive analysis.