Sentry Bugfix

Triage Sentry errors for one environment, trace a finding to current code, reproduce it locally, and deliver a focused fix PR. Use when sweeping an environment's errors, decomposing catch-all log or 5xx issues, or driving a supplied Sentry issue to a fix. Use sentry-perf for latency and gh-ci-triage for CI.

23 stars 1 forksGit & Code Review

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add jpoehnelt/skills --skill sentry-bugfix
Manual install
git clone --depth 1 https://github.com/jpoehnelt/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/sentry-bugfix ~/.claude/skills/sentry-bugfix

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Sentry-driven bug fixing

Repo facts (read from AGENTS.md or CLAUDE.md; verify in Sentry before use): Sentry organization and region, project slugs per app or runtime, environment names and the hosts they serve, where Sentry is initialized, which logger mirrors logs into Sentry, redacted fields, and the repo's check and PR commands.

Discover the callable Sentry tools first (typically issue search, event search over `errors`/`logs`/`spans`, and a resource fetch for issues and traces). Never reuse another repository's coordinates.

## Establish scope

- Resolve organization, project, and environment from the supplied issue, the connected account, and the repo's release configuration. Confirm ownership in Sentry.
- Put an explicit environment and time range on every query. Preview and CI environments often carry heavy end-to-end and accessibility-test volume; keep them out of production sweeps. If several deployments share one environment tag, separate them by host, release, or deploy evidence.
- Read the instrumentation: framework error hooks (server and client), explicit `captureException` calls, structured-logger mirrors, and process-boundary handlers in background workers. Know every path that can create an event before counting events.

## Grouping traps
Read the full skill on GitHub

Details

Skill name
sentry-bugfix
Path
sentry-bugfix/SKILL.md
License
MIT
Repo updated
12 November 2026

FAQ

What does the Sentry Bugfix skill do?

Triage Sentry errors for one environment, trace a finding to current code, reproduce it locally, and deliver a focused fix PR. Use when sweeping an environment's errors, decomposing catch-all log or 5xx issues, or driving a supplied Sentry issue to a fix. Use sentry-perf for latency and gh-ci-triage for CI.

How do I install the Sentry Bugfix skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add jpoehnelt/skills --skill sentry-bugfix. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Sentry Bugfix popular?

It lives in jpoehnelt/skills, which has 23 GitHub stars and 1 forks.

Related skills

Agents Correct

23

jpoehnelt/skills

Find the mistakes agents keep repeating in a repo and make each one impossible, trying architecture first, then types, lint, tests, and docs last. Use when the operator keeps correcting the same mistake, or for /agents-correct.

AI, LLMs & Agents

Agents Create Verification Skill

23

jpoehnelt/skills

Generate a project-local verify skill that drives the app like a user through a browser with Playwright, a CLI, or HTTP. Use for /agents-create-verification-skill, "make a verify skill for this repo", or when a project has no scripted way to prove UI, CLI, or service behavior.

AI, LLMs & Agents

Agents Reflect

23

jpoehnelt/skills

After a work session, review what went wrong and right and turn each lesson into a concrete edit to an existing skill or AGENTS.md line. Use when the user says "reflect" or /agents-reflect.

AI, LLMs & Agents

Abrir PR

9

vcampitelli/slides-agente-skills-de-verdade

Abre ou atualiza um Pull Request no GitHub para a branch atual usando o CLI `gh`, sempre como Draft, com título e corpo em português brasileiro vinculados a uma issue. Use sempre que o usuário pedir para "abrir PR", "criar pull request", "subir PR", "fazer PR dessa branch", "atualizar o PR" ou similar — mesmo que ele não diga explicitamente qual issue referenciar, pois a skill tenta detectar automaticamente. Não use para apenas commitar ou dar push (a skill nunca faz isso), nem para revisar/mergear PRs existentes.

Git & Code Review

Gh PR Feedback Loop

23

jpoehnelt/skills

Publish a GitHub pull request and carry it through CI, review feedback, rebases, and merge readiness, merging only with explicit authorization. Use when opening or updating a PR, addressing review comments, monitoring checks, rebasing, or continuing a PR to a terminal state. For read-only review of new commits, use gh-pr-commit-review.

Git & Code Review

Navigating Github to Konflux Pipelines

9

konflux-ci/agent-plugins

Use when GitHub PR or branch has failing checks and you need to find Konflux pipeline information (cluster, namespace, PipelineRun name). Teaches gh CLI commands to identify Konflux checks (filter out Prow/SonarCloud), extract PipelineRun URLs from builds and integration tests, and parse URLs for kubectl debugging.

Git & Code Review18

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.