Gpd Error Patterns

<execution_context>

<required_reading> Read all files referenced by the invoking prompt's execution_context before starting. </required_reading>

test -f .gpd/ERROR-PATTERNS.md && echo "EXISTS" || echo "MISSING"

If MISSING:

No error patterns recorded yet.

Error patterns are captured by $gpd-debug when root causes are confirmed.
They help the verifier and planner proactively check for recurring issues.

---

Start a debugging session with $gpd-debug to begin building the pattern database.

Exit. </step>

Parse the patterns table. Each row contains:

| Date | Phase | Category | Severity | Pattern | Root Cause | Prevention | </step>

Normalize the category argument to match known categories:

If category not recognized:

Unknown category: "{input}"

Available categories: sign, factor, convention, numerical, approximation, boundary, gauge, combinatorial

Usage: $gpd-error-patterns [category]

Exit.

Filter the patterns table to show only rows matching the category. </step>

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 GPD > ERROR PATTERNS: {CATEGORY}
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

| Date | Phase | Severity | Pattern | Root Cause | Prevention |
|------|-------|----------|---------|------------|------------|
{filtered rows}

---

Showing {N} of {total} patterns. Run `$gpd-error-patterns` to see all.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 GPD > ERROR PATTERNS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

## Summary

| Category | Count | Most Recent |
|----------|-------|-------------|
| sign | {N} | {date} |
| factor | {N} | {date} |
| convention | {N} | {date} |
{... for each category with entries}

## All Patterns

| Date | Phase | Category | Severity | Pattern | Root Cause | Prevention |
|------|-------|----------|----------|---------|------------|------------|
{all rows}

---

{total} patterns recorded. Filter by category: `$gpd-error-patterns sign`

───────────────────────────────────────────────────────────────

**Also available:**
- `$gpd-error-patterns <category>` -- filter by category
- `$gpd-debug` -- start a debugging session (records new patterns)
- `$gpd-verify-work` -- run verification (checks against known patterns)
- `gpd pattern search "<keyword>"` -- search global cross-project pattern library
- `gpd pattern list` -- list all global patterns (from all projects)

───────────────────────────────────────────────────────────────

<success_criteria>

• ERROR-PATTERNS.md existence checked
• Missing file handled with helpful message
• Category filter applied correctly (if provided)
• Unknown categories rejected with available list
• Patterns displayed in structured table format
• Summary by category shown (when displaying all)
• Count and filter instructions provided

</success_criteria>

@.gpd/ERROR-PATTERNS.md </execution_context>

Pre-flight check:

if [ ! -d ".gpd" ]; then
  echo "Error: No GPD project found. Run $gpd-new-project first."
  exit 1
fi

If MISSING:

No error patterns recorded yet.

Error patterns are captured by $gpd-debug when root causes are confirmed.
They help the verifier and planner proactively check for recurring issues.

---

Start a debugging session with $gpd-debug to begin building the pattern database.

Exit. </step>

If $ARGUMENTS provided (category filter):

Filter the patterns table to show only rows matching the category. Display:

## Error Patterns: {category}

{filtered table rows}

---

Showing {N} of {total} patterns. Run `$gpd-error-patterns` to see all.

If no arguments (show all):

Display the full contents formatted as:

## Project Error Patterns

{full table}

---

{total} patterns recorded. Filter by category: `$gpd-error-patterns sign`

/home/qol/.gpd/venv/bin/python -m gpd.runtime_cli --runtime codex --config-dir ./.codex --install-scope local pattern init 2>/dev/null || true
DOMAIN=$(grep -m1 "domain:" .gpd/PROJECT.md 2>/dev/null | sed 's/.*: *//' || echo "")
GLOBAL=$(/home/qol/.gpd/venv/bin/python -m gpd.runtime_cli --runtime codex --config-dir ./.codex --install-scope local --raw pattern list ${DOMAIN:+--domain "$DOMAIN"} 2>/dev/null)

If global patterns exist (count > 0), append:

## Cross-Project Patterns

{pattern list from global library, sorted by severity}

---

Global library: {count} patterns. Search: `gpd pattern search "keyword"`