gpd-regression-check

Re-verify previously verified physics claims across project phases to detect regressions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Changes introduced in later research phases can silently invalidate results that were verified in earlier phases through notation drift, convention changes, or modified shared artifacts. This Skill re-checks every claim marked VERIFIED in phase VERIFICATION.md files against the current project state so silent breakages are caught before the research narrative becomes internally inconsistent. ## Core Features & Use Cases - Verified Target Extraction: Discovers all VERIFICATION.md files under .gpd/phases, extracts VERIFIED claims, and categorizes them as dimensional, limiting_case, symmetry, conservation, numerical, artifact, analytical, or comparison targets. - Cross-Phase Consistency Checks: Detects notation drift, approximation regime violations, and modified upstream derivations by comparing conventions and git history across phases. - Severity-Classified Reporting: Generates .gpd/REGRESSION-REPORT.md with regressions classified as CRITICAL, MAJOR, or MINOR, a phase impact map, and a recommended fix order. - Use Case: After completing phase 5 of a physics derivation project, run the regression check to confirm that the dispersion relation verified in phase 2 still holds given convention changes made in phase 4. ## Quick Start Ask the AI to run the gpd regression check across all completed phases, or pass a phase number to limit the scope, and review the generated REGRESSION-REPORT.md.

Frequently Asked Questions about gpd-regression-check

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

FAQPage Schema
How do I check for regressions in verified physics results?▼

Run the regression check with no arguments to re-verify all VERIFIED targets across every completed phase, or pass a phase number to limit scope. It reads each phase's VERIFICATION.md, re-checks claims against the current project state, and writes results to .gpd/REGRESSION-REPORT.md.

What kinds of regressions does the GPD regression check detect?▼

It detects missing or stubbed artifacts, dimensional inconsistencies, limiting-case failures, notation drift between phases, approximation regime violations, modified upstream derivations, and broken conservation or symmetry claims. Each regression is classified as CRITICAL, MAJOR, or MINOR.

Can I run the regression check on a single phase only?▼

Yes, pass the phase number as an argument to scope the re-check to that phase's VERIFICATION.md only. If the phase is not found, the command reports the error and lists available phases before exiting.

How does the regression check handle projects with many phases?▼

For projects with 6 or more phases, it processes VERIFICATION.md files in batches of 3 to 5 to stay within context limits. Batch results are merged into a single running tally before classification and report generation.

What happens when a regression is found in an early phase?▼

The check traces the provides/consumes dependency chain to identify which downstream phases are affected. The report includes a phase impact map and a recommended fix order so critical regressions are resolved before dependent phases are re-verified.