error-tracking

Initialize Sentry v8 and capture errors with context across services.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/g00hyun/okky-vibe-aaa --skill error-tracking-g00hyun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error-tracking
Source: https://github.com/g00hyun/okky-vibe-aaa/tree/main/.claude/skills/error-tracking
Command: npx skills add https://github.com/g00hyun/okky-vibe-aaa --skill error-tracking-g00hyun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture and monitor errors across services using Sentry v8 to ensure visibility and quick remediation.

Core Features & Use Cases

  • Integrates Sentry v8 across services to capture errors, performance spans, and transaction data.
  • Provides patterns for controller and route error handling, cron jobs, workflow errors, and database performance monitoring.
  • Applies to both form and email services to standardize error telemetry and tracing.

Quick Start

Import the instrument.ts initialization file at startup and verify that a test error is captured by Sentry.

Frequently Asked Questions about error-tracking

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I integrate Sentry v8 for error tracking across controllers and cron jobs?

To implement Sentry v8 error tracking, import the instrument.ts initialization file at startup and wrap controller and cron job code in try/catch blocks with contextual data to capture exceptions across services.

What is the best way to monitor database performance and transactions using Sentry?

Monitoring database performance with Sentry requires instrumenting transactions and performance spans within your database queries to capture telemetry and trace execution times across form and email services.

Can I use this Sentry integration to track workflow errors in email and form services?

Yes, you can track workflow errors in email and form services by standardizing error telemetry and tracing, applying specific patterns to capture exceptions and monitor performance spans across these services.

How does initializing Sentry with an instrument file capture application errors?

Initializing Sentry with an instrument file captures application errors by setting up the Sentry v8 SDK at startup, allowing you to verify that test errors are successfully captured and reported for quick remediation.

Do I need to wrap route handlers in try/catch blocks for Sentry to capture context?

Yes, wrapping route handlers in try/catch blocks is required to provide Sentry with contextual data, ensuring that runtime exceptions and workflow errors are captured with sufficient detail for tracing.