code-check-observability-coverage

What problem does it solve?

It identifies missing or unreliable observability in changed code so you can prevent “mysterious failures” and debugging blind spots in production.

Core Features & Use Cases

• Read-only coverage audit: Detects logging gaps, swallowed errors, missing correlation IDs, PII leakage in logs, and missing latency/failure metrics without auto-instrumenting.
• Change-scoped analysis: Focuses on critical-path code and newly added/modified server entry points, webhooks, and background jobs to reduce noise.
• Severity-ranked findings: Reports HIGH/MEDIUM/LOW findings with file and line references to guide safe follow-up work.
• Logger-aware guidance: Detects which logging framework the repo uses and recommends fixes that match that existing setup.

Quick Start

Run the observability coverage audit after critical-path changes (server functions, route handlers, webhooks, or background jobs) to get a severity-ranked report of logging, error-handling, correlation, PII, and metrics gaps.