skills.rest
Cheggin
ChegginCOMMUNITY
Explore all skills by this author →
Website𝕏@reagan_hsuGitHub

error-tracking

Capture, deduplicate, and alert on frontend and backend errors with deploy-version tagging.

1|1|Updated Apr 13, 2026
Search Tags:#frontend#backend#deduplication#alerting#sentry#issue-management#error-tracking
One-click install
npx skills add https://github.com/Cheggin/request-for-startups --skill error-tracking-cheggin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: error-tracking
Source: https://github.com/Cheggin/request-for-startups/tree/main/skills/error-tracking
Command: npx skills add https://github.com/Cheggin/request-for-startups --skill error-tracking-cheggin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Integrates Sentry-based error tracking across frontend and backend apps to capture, deduplicate, and alert on issues with deploy-version tagging.

Core Features & Use Cases

  • Capture and categorize errors from frontend and backend
  • Deduplicate similar errors into a single issue with context
  • Route errors to the appropriate owner based on source and deployment
  • Detect error spikes and alert via Slack or incident response workflows
  • Tag errors with deploy version to identify regressions

Quick Start

Configure DSN, install the frontend and backend SDKs, and wire the error-tracking hooks to start collecting and routing errors.

Frequently Asked Questions about error-tracking

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

FAQPage Schema
How do I configure Sentry error tracking for both frontend and backend applications?▼

To configure Sentry error tracking, set up the DSN, install the frontend and backend SDKs, and wire the error-tracking hooks to start capturing, deduplicating, and routing errors with deploy-version tagging.

How does error deduplication work when tracking issues across web apps and APIs?▼

Error deduplication groups similar errors from web apps and APIs into a single issue, preserving context to streamline triage and prevent duplicate alerts from overwhelming incident response workflows.

Can I automatically route errors to specific owners based on deployment source?▼

Yes, error routing automatically directs captured errors to the appropriate owner based on the source and deployment, ensuring issues reach the correct team for triage and resolution.

What is the best way to detect error spikes and alert via Slack or incident workflows?▼

The best way to detect error spikes is by configuring error tracking to monitor traffic patterns and trigger automatic alerts via Slack or incident response workflows when spikes occur.

How do I tag errors with deploy versions to identify regressions across releases?▼

Tag errors with deploy versions by configuring release tracking in your SDKs, which identifies regressions by mapping captured errors to specific deploy versions across frontend and backend releases.

Do I need source maps to track frontend errors accurately in production?▼

Yes, source maps are required to de-obfuscate minified frontend code, ensuring error tracking accurately captures, classifies, and deduplicates original source code context for triage.

Related Skills

Explore More Software Engineering Skills→
dennisonbertramdennisonbertram
1

sentry-setup

Automate Sentry SDK setup, source maps, and releases for Go and JavaScript apps.

Community
Advanced
clawpod-appclawpod-app
46

incident-response

Analyze production incident metrics and output rollback recommendations.

Community
Intermediate
lapc506lapc506
4

Alerting & Incident Management

Implement alerting and incident response workflows with Prometheus, Alertmanager, and PagerDuty.

Community
Advanced
ginkidaginkida
20

sentry

Instrument production errors with Sentry SDK integration and release tagging.

Community
Intermediate