Skip to main content
configure-sentry 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.
Ir a la instalación Skills Marketplace Descubre y explora habilidades de IA creadas por la comunidad.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Mostrar detalles del prompt Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.
npx skills add https://github.com/laurigates/claude-plugins --skill configure-sentryEl comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.
¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.
Descargar Zip Descargando... Más de este repositorio Install, configure and troubleshoot MCP servers. Use when adding/enabling servers, editing .mcp.json, fixing OAuth, or when a server runs stale code after an upstream fix.
FinOps snapshot — org billing, workflow stats, cache usage. Use when you want a high-level view of CI spending or workflow health before diving deeper.
GitHub Actions billing, workflow efficiency, and waste analysis at org or repo level. Use when investigating CI/CD costs, wasted runs, or optimizing triggers.
Explorador de archivos
2 archivos Ocupaciones relacionadas SOC
Basado en la clasificación ocupacional SOC
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
Env files referencing DSN: !find . \( -name '.env*' -o -path '*/.github/workflows/*' \) -type f -exec grep -l 'SENTRY_DSN' {} +
CI workflows: !find . -path '*/.github/workflows/*' -maxdepth 3 -name '*.yml' Skills referenced : sentry (MCP server for Sentry API)
Parameters Parse these from $ARGUMENTS:
Flag Description --check-onlyReport status without offering fixes --fixApply all fixes automatically without prompting --type <type>Override project type detection (frontend, nextjs, python, node)
Version Checking CRITICAL : Before configuring Sentry SDKs, verify latest versions:
@sentry/vue / @sentry/react : Check npm @sentry/nextjs : Check npm @sentry/node : Check npm sentry-sdk (Python): Check PyPI @sentry/vite-plugin : Check npm Use WebSearch or WebFetch to verify current SDK versions before configuring Sentry.
Execution Execute this Sentry compliance check:
Step 1: Detect project type Determine the project type to select the appropriate SDK and configuration:
Read .project-standards.yaml for project_type field
If not found, auto-detect:
nextjs : Has package.json with next dependency (check for @sentry/nextjs)frontend : Has package.json with vue/react dependencies (without Next.js)node : Has package.json with Node.js backend (express, fastify, etc.)python : Has pyproject.toml or requirements.txt
If --type flag is provided, use that value instead
Step 2: Check SDK installation Check for Sentry SDK based on detected project type:
@sentry/nextjs in package.json dependencies@sentry/profiling-node (recommended for server profiling)
@sentry/vue or @sentry/react in package.json dependencies@sentry/vite-plugin for source maps
@sentry/node in package.json dependencies@sentry/profiling-node (recommended)
sentry-sdk in pyproject.toml or requirements.txtFramework integrations (django, flask, fastapi)
Step 3: Analyze configuration Read the Sentry initialization files and check against the compliance tables in REFERENCE.md . Validate:
DSN comes from environment variables (not hardcoded)
Tracing sample rate is configured (different for prod vs dev)
Source maps are enabled (frontend/Next.js)
Init location is correct (Node.js: before other imports)
Framework integration is enabled (Python)
Additional checks for Next.js projects:
src/instrumentation.ts exists with register() and onRequestError exportssrc/instrumentation-client.ts exists with client-side Sentry initsentry.server.config.ts and sentry.edge.config.ts exist at project rootnext.config.mjs wraps config with withSentryConfig()Tunnel route configured (tunnelRoute: "/monitoring")
Source maps hidden and deleted after upload (hideSourceMaps, deleteSourcemapsAfterUpload)
@sentry/profiling-node listed in serverExternalPackagesError boundaries exist (src/app/error.tsx, src/app/global-error.tsx)
Structured logging enabled (enableLogs: true)
Sensitive header stripping in beforeSend
Transaction filtering in beforeSendTransaction (drop health checks, static assets)
Step 4: Run security checks
Verify no hardcoded DSN in any source files
Check that DSN is not committed in git-tracked files
Verify no auth tokens in frontend code
Check production sample rates are reasonable (not 1.0)
Step 5: Report results Print a compliance report with:
Project type (detected or overridden)
SDK version and installation status
Configuration check results (PASS/WARN/FAIL)
Security check results
Missing configuration items
Recommendations
If --check-only, stop here.
Step 6: Apply fixes (if --fix or user confirms)
Missing SDK : Add appropriate Sentry SDK to dependenciesMissing Vite plugin : Add @sentry/vite-plugin for source mapsMissing config file : Create Sentry initialization file using templates from REFERENCE.md Hardcoded DSN : Replace with environment variable referenceMissing sample rates : Add recommended sample rates
Step 7: Check CI/CD integration Verify Sentry integration in CI/CD:
SENTRY_AUTH_TOKEN secret configuredSource map upload step in build workflow
Release creation on deploy
If missing, offer to add the recommended workflow steps from REFERENCE.md .
Step 8: Update standards tracking Update or create .project-standards.yaml:
standards_version: "2025.1"
project_type: "<detected>"
last_configured: "<timestamp>"
components:
sentry: "2025.1"
Environment Variables Variable Description Required SENTRY_DSNSentry Data Source Name (server-side) Yes NEXT_PUBLIC_SENTRY_DSNSentry DSN for client-side (Next.js) Next.js only SENTRY_ENVIRONMENTEnvironment name (server-side) Recommended NEXT_PUBLIC_SENTRY_ENVIRONMENTEnvironment name (client-side, Next.js) Next.js only SENTRY_ORGSentry organization slug For source maps SENTRY_PROJECTSentry project slug For source maps SENTRY_AUTH_TOKENAuth token for CI/CD For source maps NEXT_PUBLIC_SENTRY_SKIP_BUILDSkip Sentry webpack plugin in builds Container builds
Never commit DSN or auth tokens. Use environment variables or secrets management.
For detailed configuration check tables, initialization templates, and CI/CD workflow examples, see REFERENCE.md .
Agentic Optimizations Context Command Quick compliance check /configure:sentry --check-onlyAuto-fix all issues /configure:sentry --fixFrontend project only /configure:sentry --type frontendNext.js project /configure:sentry --type nextjsPython project only /configure:sentry --type pythonNode.js project only /configure:sentry --type nodeCheck for hardcoded DSNs rg -l 'https://[a-f0-9]*@.*sentry\.io' --type-not env
Error Handling
No Sentry SDK : Offer to install appropriate SDK for project typeHardcoded DSN : Report as FAIL, offer to fix with env var referenceInvalid DSN format : Report error, provide DSN format guidanceMissing Sentry project : Report warning, provide setup instructions
See Also
/configure:instrumentation - Whole observability stack (OTel traces/metrics, structured logging); delegates Sentry gaps to this skill/configure:all - Run all compliance checks/configure:status - Quick compliance overview/configure:workflows - GitHub Actions integrationtypescript-plugin:typescript-sentry - Day-to-day Sentry SDK usage for Bun/Node.js/Next.js (spans, breadcrumbs, cron monitoring, replay)sentry MCP server - Sentry API access for project verification 