fix-sentry

fix-sentry is a skill for Claude Code, Codex from EricTechPro/startup-claude-skills. It costs 75 tokens per session (5,594 once invoked), scanned A, original, MIT.

A workflow for investigating and fixing unresolved errors reported by Sentry, a service that monitors software failures in production.

In plain words
What is it for?
Use it to scan Sentry issues, identify shared causes, implement fixes with test-driven development, review the changes, deploy them, and resolve the incidents.
Why use it?
It groups related failures and guides the work from diagnosis through testing, deployment, and marking the errors resolved.

Skill for Claude CodeCodex

Which agent this was written for is unclear — built for gstack. Also seen: mentions CLAUDE.md; mentions subagents; built for gstack.

Good fit Use it to scan Sentry issues, identify shared causes, implement fixes with…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/erictechpro/startup-claude-skills/fix-sentry
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add EricTechPro/startup-claude-skills --skill fix-sentry
Clone the repo
git clone --depth 1 https://github.com/EricTechPro/startup-claude-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for fix-sentry

README.md
[![agentmods](https://agentmods.dev/badge/skills/erictechpro/startup-claude-skills/fix-sentry.svg)](https://agentmods.dev/skills/erictechpro/startup-claude-skills/fix-sentry)
Your own site
<a href="https://agentmods.dev/skills/erictechpro/startup-claude-skills/fix-sentry"><img src="https://agentmods.dev/badge/skills/erictechpro/startup-claude-skills/fix-sentry.svg" alt="Measured on agentmods" height="20"></a>
Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,594 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00075 $0.05594
Opus 5 $0.00037 $0.02797
Sonnet 5 $0.00015 $0.01119
Haiku 4.5 $0.00007 $0.00559

Measured 7d ago against content hash 7f6214919192, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

fix-sentry scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/fix-sentry/SKILL.md · 614 lines

How it starts

The opening of the file, as written. The whole thing — 614 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Fix Sentry Errors

Proactively scan Sentry for all unresolved errors, group them by root cause, create a unified fix plan, implement with TDD, review, deploy, and resolve the issues in Sentry.

Prerequisites

Read CONFIG.md at the start of every run. This file contains project-specific Sentry settings (org slug, project slug, region URL, deploy provider). If CONFIG.md doesn't exist, warn the user and point them to CONFIG.template.md.

When to Use

  • User wants to proactively fix production errors from Sentry
  • User says "fix sentry errors", "scan sentry", "sentry cleanup"
  • Periodic maintenance to clear unresolved Sentry issues

Parameters

Parameter Default Description
branch ask Branch strategy: ask (prompt user), worktree (isolated worktree), main (commit directly to main)

Pipeline Overview

Phase 1: Fetch all unresolved errors from Sentry
Phase 2: Triage & group by root cause → ⛔ USER GATE
Phase 3: Diagnose each group (parallel agents) → ⛔ USER GATE
Phase 4: Create unified fix plan (writing-plans)
Phase 5: Implement with TDD (executing-plans)
Phase 6: Review (layered dispatch)
Phase 6.1: Compatibility check (parallel agents)
Phase 6.2: Simplify (/simplify)
Phase 7: Commit & push
Phase 8: Deploy monitor (Vercel MCP polling)
Phase 9: Resolve in Sentry (with verification gate)
Phase 10: Summary

Phase 1: Fetch All Unresolved Errors

Goal: Retrieve all unresolved Sentry issues for the project.

Read Sentry config from CONFIG.md:

  • sentry.org — org slug
  • sentry.project — project slug
  • sentry.region_url — region URL (e.g., https://us.sentry.io)
  1. Search for unresolved issues using Sentry MCP:

    mcp__claude_ai_Sentry__search_issues
    - org: {sentry.org from CONFIG.md}
    - project: {sentry.project from CONFIG.md}
    - query: "is:unresolved"
    - sort: "events" (most events first)
    
  2. Cap at 25 issues. If more than 25 unresolved issues exist, fetch only the top 25 by event count and warn:

    ⚠️ Found {N} unresolved issues — fetching top 25 by event count.
    Consider running fix-sentry again for the remainder.
    

Read the full file on GitHub · 614 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 7d ago First seen · 614 lines · 75 tokens per session scan A 7f6214919192

Subscribe to this mod's changes

fix-sentry is a skill published in the GitHub repository EricTechPro/startup-claude-skills (54 stars, last pushed 3mo ago), licensed MIT. It adds 75 tokens to every session and 5,594 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens