error-tracking

Enforce Sentry v8 error capture and performance tracing across backend services.

3|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/joshka0/foxctl --skill error-tracking-joshka0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error-tracking
Source: https://github.com/joshka0/foxctl/tree/main/docs/knowledge/error-tracking
Command: npx skills add https://github.com/joshka0/foxctl --skill error-tracking-joshka0

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents missing critical production signals by enforcing comprehensive Sentry v8 error tracking and performance monitoring across your services.

Core Features & Use Cases

  • Centralized error capture rule: Ensures every error is captured to Sentry with consistent patterns rather than relying on ad-hoc logging.
  • Service-ready Sentry instrumentation: Covers initialization, workflow error helpers, controller handling, and database performance monitoring for typical application components.
  • Operational coverage: Adds required transaction/span tracing for API endpoints and mandatory cron job instrumentation for reliable performance visibility and troubleshooting.

Quick Start

Add this skill and then instrument your services so that all try/catch error paths call the provided helpers (and cron jobs import the instrumentation first) to guarantee errors are captured to Sentry.

Frequently Asked Questions about error-tracking

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

FAQPage Schema
How do I enforce Sentry v8 error tracking across all backend services?

Sentry v8 error tracking requires initializing Sentry in your services and using helper-based capture patterns for all try/catch blocks. This strict rule guarantees every error is captured to Sentry with no exceptions allowed.

What is the best way to instrument cron jobs for Sentry error tracking?

Instrumenting cron jobs for Sentry error tracking requires importing the instrumentation module first before execution. This mandatory tracing ensures reliable performance visibility and captures operational failures directly to Sentry.

How does database query performance monitoring work with Sentry v8?

Database query performance monitoring uses span and transaction tracing applied to your database queries. This provides reliable performance visibility and troubleshooting capabilities for your backend systems.

Do I need to add transaction tracing for API endpoints in Sentry?

Yes, adding required transaction and span tracing for API endpoints is necessary. This operational coverage ensures reliable performance visibility and effective troubleshooting across controller and route error handling.

Can I use ad-hoc logging instead of centralized error capture for Sentry?

No, you cannot use ad-hoc logging. The skill enforces centralized error capture with consistent helper-based patterns rather than relying on ad-hoc logging, preventing missing critical production signals across your services.