error-tracking

Standardize Sentry error reporting and performance tracing across services.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/fredpope/bench --skill error-tracking-fredpope
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error-tracking
Source: https://github.com/fredpope/bench/tree/main/.claude/skills/error-tracking
Command: npx skills add https://github.com/fredpope/bench --skill error-tracking-fredpope

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes and centralizes error reporting across services with Sentry v8, ensuring every error is captured and surfaced for alerting and debugging.

Core Features & Use Cases

  • Sentry initialization across services to enable performance monitoring and error capture.
  • Consistent error handling patterns in controllers, routes, cron jobs, and workflow code.
  • Cron job and database monitoring with trace spans and contextual data to diagnose failures quickly.
  • Use Case: When adding a new service or modifying existing endpoints, apply this skill to ensure all errors are reported and performance is tracked.

Quick Start

Initialize Sentry in your service (e.g., blog-api) using the provided instrument.ts file, import the helper utilities, and wrap risky operations with try/catch to route errors to Sentry. Then verify endpoints by triggering test errors as described in the docs.

Frequently Asked Questions about error-tracking

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

FAQPage Schema
How do I implement Sentry error tracking consistently across Node services?

Sentry error tracking across Node services requires standardizing initialization, wrapping controllers and cron jobs with consistent error handling patterns, and adding trace spans to capture contextual data for alerting and debugging.

How do I monitor cron jobs and database operations with Sentry in TypeScript?

Monitoring cron jobs and database operations with Sentry in TypeScript involves adding performance trace spans and contextual data to your workflow code, ensuring failures are surfaced quickly for diagnosis.

Does this Sentry error tracking approach work with controllers and routes?

Sentry error tracking works with controllers and routes by applying standardized error handling patterns that route exceptions to Sentry, ensuring every error is captured and surfaced for alerting and debugging.

What's the best way to standardize error reporting across multiple Node services?

Standardizing error reporting across multiple Node services requires centralizing Sentry v8 initialization, enforcing consistent error handling in controllers and cron jobs, and capturing contextual data to diagnose failures quickly.

Why are errors not being captured consistently across my Node services?

Errors are not captured consistently across Node services when Sentry initialization is missing or error handling patterns vary between controllers, routes, and cron jobs, preventing reliable alerting and debugging.