// Audit code for observability gaps — debug logs left in, errors caught without being logged, missing context on log entries, untracked slow operations. Uses the app's existing observability tooling exclusively.
Interview-driven planning methodology that produces implementation-ready plans. Always use this skill INSTEAD of EnterPlanMode — it provides structured interviewing (20-40 clarifying questions), exhaustive parallel codebase exploration (5-15 Explore agents), verbatim requirements capture, and automated plan validation via plan-reviewer (must score 9+). Use for new features, refactoring, architecture changes, migrations, or any non-trivial implementation work.
Audit code for silent error swallowing, fallbacks to degraded alternatives, backwards compatibility shims, and UI that fails to show errors to the user. Finds and fixes all occurrences in the specified scope.
Audit UI code for missing loading states, empty states, and error states. Every async operation and data-driven UI must handle all three. Finds gaps and implements the missing states using the app's existing patterns.
Scan all .md files in the project and add or fix YAML frontmatter (summary + read_when) so they can be discovered by context routers like Reflex.
Create or update .meridian/docs/ knowledge files for a module or directory. Produces reference docs with frontmatter for context routing.
| name | observability-audit |
| description | Audit code for observability gaps — debug logs left in, errors caught without being logged, missing context on log entries, untracked slow operations. Uses the app's existing observability tooling exclusively. |
Code that works locally but is impossible to debug in production. This skill finds and fixes observability gaps using whatever tools the app already has.
Before anything else, explore the codebase to understand what's already in use:
logger or telemetry utilities?Read how they're configured and how they're used in existing code. All fixes must use these — never introduce a new observability dependency or pattern.
Debug artifacts left in production code:
console.log, console.debug, console.info that aren't part of the established logging patternErrors that disappear:
catch(e) that propagates or re-throws without logging first — the error reaches the user but leaves no trace for debugginglogger.error(e) alone, with no info about what operation failed, what inputs were involved, or what the user was doingMissing context on log entries:
Untracked slow or critical operations:
console.log goes away entirely — no conversion to structured log, just deletedreferences/observability-patterns.md — Detection patterns, bad/fix examples for debug artifacts, missing logging, missing context, untracked operations. Read before starting the audit.Summarize by file: what was removed, what was added or improved, what context was missing and is now included.