gpd-error-patterns

Displays accumulated physics error patterns from the project error database with optional category filtering.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Physics and simulation projects accumulate recurring failure modes (sign errors, missing factors, convention mismatches) that are easy to reintroduce. This Skill surfaces the recorded error patterns from .gpd/ERROR-PATTERNS.md so verifiers, planners, and executors can proactively check for recurrence before repeating past mistakes. ## Core Features & Use Cases - Pattern viewing: Reads and displays the full error patterns table with date, phase, category, severity, root cause, and prevention columns. - Category filtering: Filters patterns by one of eight categories (sign, factor, convention, numerical, approximation, boundary, gauge, combinatorial), rejecting unknown categories with a usage message. - Cross-project library: Queries the global GPD pattern library via the runtime CLI, optionally scoped to the project domain, and appends relevant cross-project patterns sorted by severity. - Use Case: Before running a verification pass on a turbulence simulation module, a developer reviews all recorded numerical and convention error patterns to confirm the current code does not repeat previously confirmed root causes. ## Quick Start Ask the assistant to show all recorded physics error patterns, or to show only the patterns in a specific category such as sign or numerical.

Frequently Asked Questions about gpd-error-patterns

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

FAQPage Schema
How do I view recorded physics error patterns in a GPD project?▼

Run the error patterns command with no arguments to display the full table from .gpd/ERROR-PATTERNS.md, including a per-category summary with counts and most recent dates. If the file does not exist, the command explains that patterns are recorded by the debugger after root causes are confirmed.

How to filter error patterns by category like sign or numerical?▼

Pass the category name as an argument, for example sign, factor, convention, numerical, approximation, boundary, gauge, or combinatorial. The output shows only matching rows with a count of shown versus total patterns. Unknown categories are rejected with the list of valid options.

What happens when no error patterns file exists yet?▼

The command checks for .gpd/ERROR-PATTERNS.md first and, if missing, prints a message explaining that no patterns are recorded yet and suggests starting a debugging session to begin building the pattern database. It then exits without error.

Does the error patterns command include patterns from other projects?▼

Yes, it queries the global cross-project pattern library through the GPD runtime CLI, optionally filtered by the domain declared in .gpd/PROJECT.md. Matching global patterns are appended in a separate section sorted by severity.

Why does the error patterns command fail with a GPD project error?▼

The command requires an initialized GPD project with a .gpd directory. If that directory is missing, the pre-flight check fails and instructs you to run the new-project setup first before any pattern operations can work.