What problem does it solve? Teams that install Sentry often assume error tracking works, only to discover missing source maps, collapsed environments, or absent release naming after shipping. This Skill audits an existing Sentry integration and turns scattered configuration into a focused release-readiness triage plan. ## Core Features & Use Cases - Surface Inventory: Runs a helper script to detect Sentry packages, config files, environment variables, and release or source-map hooks across the repo. - Release Hygiene Review: Checks intentional release naming, distinguishable environment tags, and source-map upload timing before errors occur. - Integration Drift Detection: Flags configs without runtime initialization, missing DSN or auth tokens, and ad hoc captureException calls lacking coherent coverage. - Use Case: Before shipping a Next.js release, run the triage to confirm source maps upload in CI and environments are separated, then receive a dated triage plan under docs/observability/. ## Quick Start Ask the agent to run the Sentry release triage on this repository and write a triage plan covering release naming, environments, and source-map coverage.
