Error Tracking FAQs

Question 1

How does this skill improve my development workflow?

Accepted Answer

It removes the guesswork from error handling by providing pre-defined Sentry integration patterns. By automating the capture of user data, environment tags, and operation metadata, it significantly reduces the time required to debug and resolve production issues.

Question 2

Can I use this skill for multi-service architectures?

Accepted Answer

Yes, it is designed for multi-service projects (like Form and Email services) and includes shared configuration patterns to ensure consistent error tracking and performance metrics across your entire infrastructure.

Question 3

What does the Error Tracking skill do?

Accepted Answer

This skill automates the implementation of Sentry v8 across your project services. It provides standardized patterns for comprehensive error reporting, real-time performance monitoring, and deep context enrichment to ensure high system observability.

Question 4

When should I use this Claude Code skill?

Accepted Answer

Activate this skill whenever you are adding error handling to new code, creating API controllers, instrumenting cron jobs, or optimizing database performance. It is specifically designed to enforce a 'zero-missed-error' policy across all project services.

Question 5

What unique monitoring capabilities does it provide?

Accepted Answer

Beyond basic error logging, the skill provides specialized helpers for database performance tracking, N+1 query detection, and mandatory instrumentation for cron jobs to ensure background task reliability and execution visibility.

Error Tracking

Error Tracking

Key Features

Use Cases

Key Features

Use Cases