Agent skill · software engineering · jeremylongshore
sentry-local-dev-loop
Configure Sentry for local development with environment-aware settings.
Why this skill is useful
Adds specific configuration patterns and scripts for integrating Sentry in local development environments that the AI wouldn't reliably generate on its own.
What it needs
Requires @sentry/node, @spotlightjs/spotlight installed locally. Requires sentry account access. About 7k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Sentry Local Dev Loop Overview Configure Sentry for local development with environment-aware DSN routing, debug-mode verbosity, full-capture sample rates, beforeSend inspection, Sentry Spotlight for offline event viewing, and sentry-cli source map verification. All configuration uses environment variables so nothing leaks into commits. Prerequisites @sentry/node v8+ installed (TypeScript/Node) or sentry-sdk v2+ installed (Python) Separate Sentry project created for development (different DSN from production) .env file with SENTRYDSNDEV and NODEENV=development Network access to .ingest.sentry.io (or use Spotlight for fully offline work) Instructions Step 1 -- Environment-Aware Configuration Create an initialization file that routes events to the correct Sentry project based on environment, enables debug logging in dev, and captures 100% of traces locally: Set up environment files to keep DSNs out of source: Add DSN safety to .gitignore: Step 2 -- Local Verification and Performance Debugging Create a verification script that confirms the SDK works end-to-end and demonstrates Sentry.startSpan() for local performance profiling: Use Sentry.startSpan() in your application code to profile specific operations during development: Step 3 -- Sentry Spotlight and Offline Development Sentry Spotlight runs a local sidecar that intercepts Sentry events and displays them in a browser UI at http://localhost:8969 (Spotlight's default port) — no network required: The spotlight: true option in Step 1's Sentry.init() routes events to the local sidecar. This gives you a full Sentry-style event viewer without sending anything to sentry.io. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/sentry-local-dev-loop--f4e85b