configure-sentry

created	"2025-12-16T00:00:00.000Z"
modified	"2026-07-05T00:00:00.000Z"
reviewed	"2026-07-05T00:00:00.000Z"
description	Sentry error tracking setup. Use when installing the Sentry SDK, fixing hardcoded DSNs, or adding source map upload for frontend, Next.js, Node, or Python.
allowed-tools	Glob, Grep, Read, Write, Edit, Bash, AskUserQuestion, TodoWrite, WebSearch, WebFetch
args	[--check-only] [--fix] [--type <frontend|nextjs|python|node>]
argument-hint	[--check-only] [--fix] [--type <frontend|nextjs|python|node>]
name	configure-sentry

/configure:sentry

Check and configure Sentry error tracking integration against project standards.

When to Use This Skill

Use this skill when...	Use another approach when...
Setting up Sentry error tracking for a new project	Debugging a specific Sentry issue or alert (use Sentry MCP server)
Sentry-specific setup and compliance in depth	Wiring up the whole observability stack — OTel traces/metrics + logging (use /configure:instrumentation, which delegates Sentry gaps back here)
Checking Sentry SDK installation and configuration compliance	Querying Sentry events or performance data (use Sentry API/MCP)
Fixing hardcoded DSNs or missing environment variable references	Managing Sentry project settings in the Sentry dashboard
Adding source map upload and release tracking to CI/CD	Configuring Sentry alerting rules or notification channels
Verifying Sentry configuration across frontend, Next.js, Node.js, or Python projects	Installing a different error tracking tool (e.g., Bugsnag, Rollbar)
Adding profiling, structured logging, or enrichment helpers	Configuring Sentry alerting rules or notification channels
Project-level setup and compliance auditing	Day-to-day SDK usage patterns — spans, breadcrumbs, cron monitoring, replay (use typescript-plugin:typescript-sentry)

Context

• Package.json: !find . -maxdepth 1 -name \'package.json\'
• Pyproject.toml: !find . -maxdepth 1 -name \'pyproject.toml\'
• Requirements.txt: !find . -maxdepth 1 -name \'requirements.txt\'
• Project standards: !find . -maxdepth 1 -name '.project-standards.yaml' -type f
• Sentry in package.json: !find . -maxdepth 1 -name 'package.json' -exec grep -o '"@sentry/[^"]*"' {} +
• Sentry in pyproject.toml: !find . -maxdepth 1 -name 'pyproject.toml' -exec grep 'sentry' {} +
• Sentry init files: !find . -maxdepth 3 -name "*sentry*" -type f
• Next.js config: !find . -maxdepth 1 -name 'next.config.*'
• Instrumentation files: !find . -path '*/src/*' -maxdepth 2 -name 'instrumentation*' -type f