gpd-compare-branches

Compare research results across hypothesis branches using structured tables and statistical tension analysis.

Updated Mar 18, 2026

Search Tags:#git #verification #merge #hypothesis testing #research workflow #branch comparison #statistical tension

Ready to run

npx skills add https://github.com/MichaelsEngineering/sentinel-multiscale-field-dynamics --skill gpd-compare-branches-michaelsengineering

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gpd-compare-branches
Source: https://github.com/MichaelsEngineering/sentinel-multiscale-field-dynamics/tree/main/.agents/skills/gpd-compare-branches
Command: npx skills add https://github.com/MichaelsEngineering/sentinel-multiscale-field-dynamics --skill gpd-compare-branches-michaelsengineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When research work is split across multiple hypothesis branches, it becomes hard to decide which approach is more promising. This Skill builds a side-by-side comparison of results, verification status, and numerical outcomes across branches so you can make an evidence-based merge decision. ## Core Features & Use Cases - Branch Discovery and Extraction: Lists all hypothesis/* branches and pulls STATE.md, HYPOTHESIS.md, SUMMARY.md, and VERIFICATION.md data from each via git. - Structured Comparison Tables: Builds overview, key-results, equations, and verification tables including the parent branch as a baseline. - Numerical Tension Analysis: Computes relative differences and sigma-level tension between matched quantities, flagging statistically significant disagreements. - Use Case: After running two competing turbulence-modeling hypotheses on separate branches, invoke this Skill to compare their energy spectrum results, see a 5.4-sigma tension flagged on the critical temperature, and merge the winning branch back to main. ## Quick Start Ask the assistant to compare all hypothesis branches side-by-side and recommend which one to merge back into the parent branch.

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 results across git hypothesis branches?▼

Invoke the compare-branches workflow, which lists all hypothesis/* branches, extracts STATE.md and SUMMARY.md data from each via git show, and builds a structured comparison table including the parent branch as baseline.

How is statistical tension between branch results calculated?▼

For matched quantities with uncertainties, tension equals the absolute difference divided by the combined sigma (quadrature sum). Values without uncertainties use relative-difference thresholds: under 1% consistent, 1-5% mild, 5-10% notable, over 10% large.

Can I compare branches if only one hypothesis branch exists?▼

Yes. Single-branch mode compares the one hypothesis branch against its parent branch as the baseline, letting you evaluate a hypothesis without needing a second alternative.

What happens if a branch has no SUMMARY.md files?▼

Branches missing STATE.md are marked as having no state data. If no branch has any SUMMARY.md files, the workflow exits with a message telling you to complete at least one plan per branch before comparing.

Does the comparison merge branches automatically?▼

No. Merging, deleting, or exporting the comparison always requires explicit user confirmation. Merge conflicts trigger a checkpoint asking you to resolve them manually before continuing.

What are the limitations of branch comparison?▼

Branches with no completed plans cannot be meaningfully compared, and purely analytical branches skip the numerical comparison step. The workflow also avoids force-pushing or rebasing hypothesis branches.