register-retry-error

Register Retry Error — Skill for Error Pattern Registration

Triggers: /register-retry-error, register retry error, add retry pattern

---

WORKFLOW

1. Accept Parameters

When invoked with /register-retry-error, request or receive:

• pattern (required): The error message pattern to match (regex string)
• description (required): Human-readable explanation of the error
• max_retries (optional): Number of retries after initial attempt (default: 3)
• backoff_ms (optional): Array of delay times in milliseconds (default: [1000, 6000, 36000])
• retry_after_tool_execution (optional): Whether to retry even after tool execution (default: false)
• added_by (optional): Your identifier or "operator" (default: "operator")

2. Validate Regex Pattern

Before proceeding, validate the provided pattern:

try {
  new RegExp(pattern)
} catch (e) {
  throw new Error(`Invalid regex pattern: ${e.message}`)
}

MUST: Reject invalid patterns immediately with clear error message.

3. Generate Kebab-Case ID

Create a unique id from the description:

• Convert to lowercase
• Replace spaces and underscores with hyphens
• Remove special characters (keep only alphanumeric and hyphens)
• Limit to ~50 characters
• Ensure it matches the pattern: ^[a-z0-9]([a-z0-9-]*[a-z0-9])?$

Example:

• "Network timeout on SSE stream" → "network-timeout-on-sse-stream"
• "Provider Rate Limited" → "provider-rate-limited"

4. Check for Duplicates

Read the current registry file: ~/.config/opencode/retry-errors.json

MUST verify:

• No existing entry has the same id (duplicate key)
• No existing entry has the same pattern string (duplicate pattern)

If duplicates found, reject with reason: "Entry with id '{id}' already exists" or "Pattern already registered"