Skip to content

/find-in-sentry

Answer "what's breaking" questions from Sentry — find the right org and project, search issues and errors with the vocabulary Sentry uses, and report what is actually firing rather than the first hit. Use when the user asks what errors are happening, whether something is stable,

From plugin
paradev
16k48 skills1 agent1 command

Claude Code

$ npx -y skills add paradevai/paradev --skill find-in-sentry --agent claude-code

SKILL.md

find-in-sentry.SKILL.md
name: find-in-sentry
description: Answer "what's breaking" questions from Sentry — find the right org and project, search issues and errors with the vocabulary Sentry uses, and report what is actually firing rather than the first hit. Use when the user asks what errors are happening, whether something is stable, what changed since a release, or for any health summary of a service.
argument-hint: the service, error, release, or question to look up
allowed-tools: mcp__sentry__find_organizations, mcp__sentry__find_projects, mcp__sentry__search_issues, mcp__sentry__search_errors, mcp__sentry__get_sentry_resource, mcp__sentry__search_sentry_tools, mcp__sentry__execute_sentry_tool

Find what is actually firing

Sentry answers precise questions precisely and vague questions misleadingly. The work is scoping the question before searching, and ranking what comes back by impact instead of by relevance.

1. Scope to the right project first

Run `find_organizations` and `find_projects` before searching if you are not certain where the code reports to. A monorepo often maps to several Sentry projects (api, web, desktop), and a search in the wrong one returns a confident, empty answer. Say which project you searched.

2. Search the way Sentry indexes, not the way people ask

"Is checkout broken?" becomes queries on what Sentry actually stores: the error type, the transaction or URL, the release. Prefer `search_issues` for "what problems exist" and `search_errors` for "how often / for whom / since when". Run two or three narrow queries over one broad one, and time-bound them — `is:unresolved` over the last 24h answers a different question than all-time.

3. Rank by impact, not by recency of the search result

The issues worth reporting are the ones with high event counts, many affected users, or a first-seen that matches a recent release. A brand-new issue with three events can matter more than a year-old one with thousands — say why the ones you picked matter. When a number is load-bearing (error rate, affected users), take it from `search_errors` rather than eyeballing the issue list.

4. Answer with links and the time window

Every issue you cite gets its Sentry link and the window you looked at. "No matching issues in the last 7 days in `api`" is a complete, useful answer — silence about scope is how "it's fine" turns out to mean "I searched the wrong project".

Anti-patterns

  • **Reporting the first page as the truth.** Sort order is not severity.
  • **Mixing environments.** Production noise and staging noise answer different

questions; filter to the environment the user cares about.

  • **Counting issues to measure health.** Ten one-off issues can be healthier

than one issue hitting every user; lead with events and users affected.

  • **Answering "is it stable" without a baseline.** Compare against the prior

window or the prior release, not against zero.

Read more
@superset-sh
Ships withparadev

Paradev is an open-source Codex App and Conductor alternative. Orchestrate an army coding agents in parallel with your own subscriptions.

Stars on GitHub

Momentum

stars in total
16.2k
Star history of superset-sh/superset on GitHub, a chart by star-history.com

Other skills on paradev.

find-in-circleback
Auto-invoked

find-in-circleback

Answer "what did we say, decide, or promise" from Circleback meetings — search by attendee, company, tag, or date before keyword,…

@superset-sh@superset-shInstall Skill
prep-with-circleback
Auto-invoked

prep-with-circleback

Build a brief for an upcoming meeting from Circleback — the calendar event, the history with the same people and company, open…

@superset-sh@superset-shInstall Skill
ci-triage
Auto-invoked

ci-triage

Diagnose a failing GitHub Actions run — find the first real error in the logs, tell a flake apart from a genuine failure, and…

@superset-sh@superset-shInstall Skill
issue-triage
Auto-invoked

issue-triage

Triage a GitHub issue into something actionable — reproduce the claim, find duplicates, judge severity, and apply labels,…

@superset-sh@superset-shInstall Skill
find-in-granola
Auto-invoked

find-in-granola

Answer "what did we say, decide, or promise" from Granola meeting notes — narrow to the meetings that can hold the answer, read…

@superset-sh@superset-shInstall Skill

More skills from other plugins.

paseo

paseo

Paseo reference for managing hosts, projects, workspaces, workspace scripts, agents, schedules, and heartbeats.

paseo11d23k
@getpaseo@getpaseoInstall Skill
capabilities

capabilities

Your capability catalog — read this at boot. Lists the temporal date-range skills and the external integrations (reached via the…

@chaitanyagiri@chaitanyagiriInstall Skill
brainstorming

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…

codeg2d4.4k
@xintaofei@xintaofeiInstall Skill

Questions about find-in-sentry.

Which coding agents can use find-in-sentry?
find-in-sentry installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.