gpd-regression-check

Scan project phase summaries for conflicting conventions and invalid verification statuses.

Updated May 1, 2026
One-click install
npx skills add https://github.com/Unified-Field-Theory-Research/finite-capacity-causal-geometry --skill gpd-regression-check-unified-field-theory-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gpd-regression-check
Source: https://github.com/Unified-Field-Theory-Research/finite-capacity-causal-geometry/tree/main/.agents/skills/gpd-regression-check
Command: npx skills add https://github.com/Unified-Field-Theory-Research/finite-capacity-causal-geometry --skill gpd-regression-check-unified-field-theory-research

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill identifies potential issues in project phase summaries and verifications, allowing for early detection of inconsistencies and regressions.

Core Features & Use Cases

  • Detect Convention Conflicts: Scans summary artifacts for conflicting convention definitions.
  • Identify Verification Issues: Finds missing, invalid, or non-canonical verification statuses.
  • Quick Audit: Efficiently scan all or specific completed phases, with an option for quick mode.
  • Use Case: Before finalizing a project phase, use this Skill to ensure all verifications are accurate and consistent.

Quick Start

Run the gpd-regression-check skill with the optional phase argument to scan a specific phase, or leave it empty to scan all completed phases.

Frequently Asked Questions about gpd-regression-check

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

FAQPage Schema
How do I detect regressions and inconsistencies in project phase summaries?

To detect regressions in project phase summaries, scan summary and verification artifacts within a project directory to automatically identify conflicting conventions, missing statuses, and unresolved gaps.

What is phase verification and summary auditing in project management?

Phase verification and summary auditing is the process of scanning completed project phases to ensure all verification statuses are accurate, canonical, and free from conflicting convention definitions before finalizing.

How do I audit specific completed phases instead of an entire project directory?

To audit specific completed phases, run the skill with an optional phase argument to target a single phase, or leave the argument empty to scan all completed phases across the project directory.

Do I need file system access to perform a project phase summary audit?

Yes, you need file system access to perform a summary audit because the skill directly scans summary and verification artifacts stored as files within your project directory structure.

Can I use a quick mode for phase verification scanning?

Yes, you can use a quick mode option for phase verification scanning to efficiently audit all or specific completed phases when you need a rapid check before finalizing.

Why does my project phase verification show invalid or non-canonical statuses?

Invalid or non-canonical verification statuses occur when summary artifacts contain unresolved gaps or deviate from established conventions, which you can identify by scanning the project directory.