Error Tracking FAQs

Question 1

When should I use this skill during development?

Accepted Answer

You should activate this skill when adding new API routes, creating background cron jobs, handling complex workflows, or optimizing database performance. It is essential whenever you need to ensure that application errors are captured with rich context rather than just logged to the console.

Question 2

What does the Error Tracking skill do for Claude Code?

Accepted Answer

This skill empowers Claude to automatically implement and maintain high-standard Sentry v8 error tracking and performance monitoring. It provides Claude with specific patterns for controller instrumentation, cron job tracking, workflow metadata capture, and database query monitoring.

Question 3

Can this skill help with database performance?

Accepted Answer

Yes. It includes specific capabilities for database performance monitoring, enabling Claude to wrap Prisma or other ORM calls with performance trackers that detect slow queries (threshold > 100ms) and identify N+1 query patterns automatically.

Question 4

Does it support modern Sentry v8 features?

Accepted Answer

Absolutely. The skill is optimized for Sentry v8, utilizing new patterns for profiling, custom performance spans, distributed tracing, and the latest transaction-based performance monitoring for distributed Node.js services.

Question 5

How does this skill improve my service's reliability?

Accepted Answer

It enforces a 'zero-exception' policy for error capturing, meaning Claude will ensure every catch block forwards data to Sentry. By automating boilerplate like instrument.ts imports for cron jobs and transaction spans for async tasks, it eliminates human error in observability setup.

Error Tracking

Error Tracking

Características Principales

Casos de Uso

Características Principales

Casos de Uso