What problem does it solve? Code reviews of observability changes often accept claims like "all calls are instrumented" based on call-site counts, missing exception paths where spans and metrics silently go unrecorded. This Skill provides a checklist that verifies path coverage rather than call-site presence when reviewing .NET tracing and metrics changes. ## Core Features & Use Cases - Filtered-catch escape detection: Identifies catch (Exception ex) when (ex is not X) filters that let guard-thrown exceptions escape without recording, and prescribes the idempotent-record fix. - Recording correctness checks: Verifies exactly-once recording, Activity status/tag ordering before span stop, and instrumentation unit-test honesty including ActivityListener parallelization flakes. - E2E parity and CI gate review: Validates tool-surface parity tests for exact set equality, cross-file call enumeration, Speed-trait CI blind spots, and metrics-unchanged diffs. - Use Case: When a PR claims "all 19 tools emit the span/metrics contract", use this Skill to walk every throw/return path, find the four tools whose access-denied errors escape unrecorded, and issue a MAJOR finding with a concrete fix. ## Quick Start Review this pull request that claims all tool calls are instrumented and verify the span and metrics contract holds on every error path.