Error Tracking FAQs

Question 1

When should I use this skill?

Accepted Answer

You should activate this skill when adding error handling to existing code, creating new controllers, instrumenting cron jobs, or optimizing database performance. It is essential for maintaining production-grade observability.

Question 2

What does the Error Tracking Claude Code skill do?

Accepted Answer

This skill automates the implementation of Sentry v8 across your project services. It enforces comprehensive error capturing and performance monitoring patterns for controllers, routes, and background tasks, ensuring no exception goes unrecorded.

Question 3

How does this skill improve my development workflow?

Accepted Answer

It eliminates manual boilerplate and the risk of 'swallowed' errors by providing standardized code patterns. It automatically suggests the correct Sentry context for workflows and ensures performance spans are added to asynchronous operations.

Question 4

What specific performance capabilities does it provide?

Accepted Answer

Beyond basic error logging, it provides advanced database monitoring (including N+1 query detection), automated performance spans for API endpoints, and mandatory execution tracking for cron jobs to identify bottlenecks.

Question 5

Why is this better than using standard console error logs?

Accepted Answer

Standard logs are often lost or ignored. This skill enforces a 'Critical Rule' where all errors must be captured to Sentry with full metadata, enabling real-time alerting and deep-dive analysis that console logs cannot provide.

Error Tracking

Error Tracking

Key Features

Use Cases

Key Features

Use Cases