Sentry
MonitoringCommonly used with
Skills using Sentry (19)
add-error-tracking
Add Temps error tracking to applications using the Sentry-compatible SDK. Temps exposes a Sentry-compatible DSN that works with the official Sentry SDK for each language/framework — no code changes beyond initialization are required. Use when the user wants to: (1) Add error tracking to any app (React, Next.js, Vue, Svelte, Angular, Node.js, Python, Go, Rust, Ruby, Java, PHP, .NET, React Native, Flutter), (2) Wire up uncaught exception and unhandled promise rejection capture, (3) Configure session replay for errors, (4) Upload source maps for readable stack traces, (5) Report releases and environments, (6) Capture custom errors/messages. Triggers: "add error tracking", "add sentry", "track exceptions", "report errors", "temps error tracking", "wire up error monitoring".
bug-analyzer
Use when the user shares a Sentry error, Jira bug ticket, or error description and wants root cause analysis. Also for proactive bug hunting and code audits for hidden bugs.
debug-sentry-monitor
Monitor, triage, fix, and proactively enhance Sentry error monitoring for any project. Use when asked to: check Sentry, fix Sentry errors, triage Sentry issues, run post-deploy monitoring, review production errors, clean up Sentry noise, audit Sentry setup, improve monitoring coverage, enhance error tracking, or "run sentry check". Works with any GitHub repo — auto-detects org, project, framework, and config. Fetches issues via Sentry MCP, triages them, performs root cause analysis, fixes code bugs, updates noise filters, audits the monitoring architecture, and resolves issues only after verified fixes.
sentry
Query Sentry organizations, projects, and unresolved issues/errors via the Sentry API. Use when the user asks about Sentry errors, issues, or projects.
claude-jobs
Find job openings at tech companies. Use when user asks about jobs, careers, openings, positions, roles, or salaries - either at specific companies or general tech job queries.
devlab-web-glitchtip-usage
前端 GlitchTip 错误追踪接入技能。凡是用户提到 GlitchTip、Sentry SDK、前端错误聚合、Source Map 上传、JS 错误追踪、Issue 管理时触发。框架无关，支持 Vue/React/Angular/Svelte/原生 JS。
rcode-dalil-scout
Codebase Scout — Dalil (دليل) — for repository discovery, multi-root exploration, focused topic sweeps, and producing structured codebase documents (STACK, ARCHITECTURE, STRUCTURE, INTEGRATIONS, CONVENTIONS, TESTING, CONCERNS). Activates when the user says "scan the codebase", "map the codebase", "what's in this repo", "discover X across the project", "audit instrumentation", "find all callers of Y", "is there any Sentry / GraphQL / Redis usage", "explore the project structure", "talk to Dalil", or "scout this repo". Also activates via /rcode-scan and /rcode-map-codebase. Do NOT use for: plan execution (use executor), strategic decisions (use Sadiq / Waleed), test design (use Fatima), or code modification (use Hanzla / Omar).
debug
Runs a structured production-incident investigation that forces evidence-first hypothesis ranking before any code change. Use when given an error message, Sentry alert, failing log, or an 'investigate <X>' request.
sentry-issue
Fetches and digests Sentry issue data (summary, tags, stack trace, breadcrumbs, latest event) by short ID, numeric issue ID, or sentry.io URL, for any Sentry org the local token can access. Use when the user mentions a Sentry issue or short ID (e.g. MY-PROJECT-4X2), pastes a sentry.io issue URL, or asks to investigate a Sentry error.
sentry
Monitor and debug application errors via the Sentry CLI. Use when triaging production errors or managing releases.
sentry
Use when user references Sentry, sentry.io URLs, *.sentry.io/issues/ links, error/exception/release alerts, pastes a stack trace for triage, or checks release health on cloud or self-hosted. Multi-org via SENTRY_PROFILE.
observability-context
Fetch production observability signals from Sentry — error, regression, and alert data. Auto-loads on Sentry references. Returns message/culprit, first-seen, always labeled as Phase-1 framing, never a profile.
sentry-triage
Query Sentry for production errors, filter by severity/frequency, deduplicate against existing GitHub issues, and create actionable issues for the implement-queue. Invoke with /sentry-triage.
read-sentry-issue
Use when a Sentry issue/event link appears, or when working with Sentry error tracking via the official Sentry MCP server, listing organizations/projects/issues, or fetching event/stacktrace details for an issue.
monitoring
Use for standalone, on-demand checks of production health, errors, performance, or uptime.
sentry
Sentry error monitoring and performance tracing patterns for Next.js applications.
glitchtip
Use when deploying, configuring, integrating, or troubleshooting GlitchTip — including self-hosted installation, SDK setup, source maps, sentry-cli, uptime monitoring, alerting, environment variables, Docker Compose, Helm, social auth, and migration from Sentry
sentry-integration
Sentry error tracking i performance monitoring dla React + Supabase Edge Functions. Aktywuje się przy pracy z błędami, monitoringiem, captureException, error boundary, śledzeniem błędów, diagnostyką, loggerem, Edge Functions, crash, awaria, wydajność, raportowanie błędów, exception, wyjątek.
triage
Runtime agent observability — pull recent Sentry errors, cluster by signature, file Linear tickets with stack traces, optionally open worktree + PR with proposed fix. Plus synthetic user-journey cron orchestration.
Integration detected automatically from skill content. Some results may be false positives.