Audits code for silent error swallowing, degraded fallbacks, backwards compatibility shims, and UI failing to show errors to users. Finds and fixes all occurrences in specified scope.
From meridiannpx claudepluginhub markmdev/meridianThis skill uses the workspace's default tool permissions.
references/error-patterns.mdGuides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.
The core principle: every error belongs to the user. Not to a catch block, not to a console, not to a null return. Scan the specified code, fix every violation, report what changed.
Before fixing anything, identify how this app surfaces errors to users — toast notifications, error banners, error boundaries, returned error states, alert dialogs, inline messages. Use these patterns exclusively. Don't invent a new one.
Silent error swallowing — backend/logic layer:
catch(e) {}catch(e) { console.error(e) } with execution proceeding normally.catch(() => {}) on promisesnull, undefined, or empty defaults on failure instead of throwingSilent error swallowing — UI layer:
try/catch in a loader or server action that swallows the error and returns partial/empty dataFallbacks to degraded alternatives:
Backwards compatibility shims:
if (legacyFormat) or if (oldVersion) branchesConfig defaults that hide misconfiguration:
process.env.X || 'fallback' for required values — missing required config is a startup crash, not a defaultOptional chaining hiding missing required data:
user?.profile?.name ?? 'Guest' when profile must always exist — the absence is a bug, not an edge case to handle silentlyreferences/error-patterns.md — Concrete anti-patterns with structural descriptions, bad/good code examples, and false positive notes. Read this before starting the audit.After fixing, summarize by file: what was found, what the fix was. Be specific — file paths and the pattern removed.