gpd-branch-hypothesis

Creates a git hypothesis branch with forked research state and hypothesis documentation.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/MichaelsEngineering/sentinel-multiscale-field-dynamics --skill gpd-branch-hypothesis-michaelsengineering
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gpd-branch-hypothesis
Source: https://github.com/MichaelsEngineering/sentinel-multiscale-field-dynamics/tree/main/.agents/skills/gpd-branch-hypothesis
Command: npx skills add https://github.com/MichaelsEngineering/sentinel-multiscale-field-dynamics --skill gpd-branch-hypothesis-michaelsengineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Researchers often need to test an alternative approach, approximation scheme, or derivation pathway without disrupting the main line of research. This Skill creates an isolated git branch with its own forked STATE.md and structured hypothesis documentation so parallel investigations stay organized and comparable. ## Core Features & Use Cases - Hypothesis Branch Creation: Generates a slug from your description, verifies a clean git state (with optional auto-stash), and creates a hypothesis/{slug} branch. - Structured Hypothesis Documentation: Writes .gpd/hypotheses/{slug}/HYPOTHESIS.md with motivation, expected outcome, and success criteria, AI-drafted from project context for researcher review. - State Forking and Tracking: Records the branch decision via the GPD CLI and annotates STATE.md so results can later be compared side-by-side with the parent branch. - Use Case: A physicist wants to compare dimensional regularization against a hard cutoff. Running this Skill creates a dedicated branch, drafts testable success criteria, and keeps the main research state untouched. ## Quick Start Ask the AI to create a hypothesis branch for investigating dimensional regularization instead of a hard cutoff using the gpd-branch-hypothesis skill.

Frequently Asked Questions about gpd-branch-hypothesis

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

FAQPage Schema
How do I create a git branch for testing an alternative research approach?▼

Run the branch-hypothesis workflow with a short description of the alternative approach. It generates a slug, verifies the git state is clean, creates a `hypothesis/{slug}` branch, and writes a HYPOTHESIS.md document with motivation and success criteria.

How to compare two approximation schemes in a physics research project?▼

Create a hypothesis branch for the alternative scheme so each approach gets its own forked STATE.md and hypothesis documentation. After executing both lines of work, use the compare-branches workflow for side-by-side comparison.

What happens if I have uncommitted changes when creating a hypothesis branch?▼

The workflow detects uncommitted changes via git status and offers to auto-stash them with a labeled stash message before continuing. You can recover the changes later with git stash pop, or abort and handle them manually.

When should I not use a hypothesis branch?▼

Avoid hypothesis branches for trivial parameter variations, which are better handled by a parameter sweep. Also do not nest hypothesis branches off other hypothesis branches; branch from the main or primary research branch instead.

Does the hypothesis branch modify the parent branch research state?▼

No. The workflow only modifies the STATE.md copy on the new hypothesis branch and records the decision through the GPD CLI. The parent branch state remains untouched, and the durable record lives in HYPOTHESIS.md plus the decision entry.