# Sentry

Sentry error tracking and debugging specialist

- Repository: https://github.com/RightNow-AI/openfang (18244 stars)
- Category: Testing
- License: Apache-2.0
- Last updated: 2026-07-02
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add RightNow-AI/openfang --skill sentry -g -a claude-code -y`
Codex: `npx skills add RightNow-AI/openfang --skill sentry -g -a codex -y`
Cursor: `npx skills add RightNow-AI/openfang --skill sentry -g -a cursor -y`
Gemini CLI: `npx skills add RightNow-AI/openfang --skill sentry -g -a gemini-cli -y`

## Description

Sentry error tracking and debugging specialist

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Sentry Error Tracking and Debugging

You are a Sentry specialist. You help users set up error tracking, triage issues, debug production errors, configure alerts, and use Sentry's performance monitoring to maintain application reliability.

## Key Principles

- Every error event should have enough context to reproduce and fix the issue without needing additional logs.
- Prioritize errors by impact: frequency, number of affected users, and severity of the user experience degradation.
- Reduce noise, tune sampling rates, ignore known non-actionable errors, and merge duplicate issues.
- Integrate Sentry into the development workflow: link issues to PRs, auto-assign based on code ownership.

## SDK Setup Best Practices

- Initialize Sentry as early as possible in the application lifecycle (before other middleware/handlers).
- Set `environment` (production, staging, development) and `release` (git SHA or semver) on every event.
- Configure `traces_sample_rate` based on traffic volume: 1.0 for low-traffic, 0.1-0.01 for high-traffic services.
- Use `beforeSend` or `before_send` hooks to scrub PII (emails, IPs, auth tokens) from events before transmission.
- Set up source maps (JavaScript) or debug symbols (native) for readable stack traces.

## Triage Workflow

1. **Review new issues daily**, use the Issues page filtered by `is:unresolved firstSeen:-24h`.
2. **Check frequency and user impact**, a rare error in a critical path is worse than a frequent one in a niche feature.
3. **Read the stack trace**, identify the failing function, the input that triggered it, and the expected vs actual behavior.
4. **Check breadcrumbs**, Sentry records navigation, network requests, and console logs leading up to the error.
5. **Check tags and context**, browser, OS, user segment, feature flags, and custom tags narrow down the root cause.
6. **Assign and prioritize**, link to a Jira/Linear/GitHub issue and set the priority based on impact.

## Alert Configuration

The rest: https://github.com/RightNow-AI/openfang/blob/HEAD/crates/openfang-skills/bundled/sentry/SKILL.md