Fix Sentry
Scan all unresolved Sentry errors, group by root cause, fix in batch with TDD, and resolve in Sentry after deploy. Use when the user says 'fix sentry errors', 'scan sentry', 'resolve sentry issues', 'fix all errors', 'sentry cleanup', or wants to proactively fix production errors from Sentry monitoring.
Install
npx skills add EricTechPro/startup-claude-skills --skill fix-sentrygit clone --depth 1 https://github.com/EricTechPro/startup-claude-skills.git /tmp/startup-claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/startup-claude-skills/skills/fix-sentry ~/.claude/skills/fix-sentryPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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
Details
- Skill name
fix-sentry- Repository
- EricTechPro/startup-claude-skills
- Path
skills/fix-sentry/SKILL.md- License
- MIT
- Repo updated
- 5 June 2026
FAQ
What does the Fix Sentry skill do?
Scan all unresolved Sentry errors, group by root cause, fix in batch with TDD, and resolve in Sentry after deploy. Use when the user says 'fix sentry errors', 'scan sentry', 'resolve sentry issues', 'fix all errors', 'sentry cleanup', or wants to proactively fix production errors from Sentry monitoring.
How do I install the Fix Sentry skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add EricTechPro/startup-claude-skills --skill fix-sentry. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Fix Sentry popular?
It lives in EricTechPro/startup-claude-skills, which has 58 GitHub stars and 18 forks.
Related skills
Develop Team
58EricTechPro/startup-claude-skills
This skill should be used when the user asks to "develop a feature", "implement a ticket", "build PROJ-123", "run the development pipeline", "develop this ticket end to end", or wants fully autonomous feature implementation with parallel research agents, planning, phased implementation, review, and PR creation. Zero checkpoints; pauses only on blockers.
Fix Ticket
58EricTechPro/startup-claude-skills
Automate the full Jira bug-fix pipeline end-to-end. Use when the user says 'fix ticket', 'fix PROJ-123', 'fix this bug', 'resolve PROJ-XXX', 'fix and ship this ticket', or passes a Jira ticket ID for autonomous bug resolution. Reads the Jira ticket, implements the fix, reviews it, commits, moves the ticket to QA, assigns to QA engineer, and comments with a summary. Also use when the user wants to automate the fix-review-commit-handoff cycle for any Jira bug ticket.
Playwright QA CLI
58EricTechPro/startup-claude-skills
Automated QA testing using playwright-cli (CLI tool, NOT MCP tools). Provisions a test user, opens a headless browser, logs in, navigates to target pages, takes screenshots, and generates a REPORT.md. Two modes: VERIFY (reproduce a bug before fixing) and CHECK (confirm a fix works). Use this skill whenever the user says 'QA this', 'test this fix', 'verify this bug', 'smoke test', 'check if this works', 'reproduce this issue', 'run playwright QA', or 'playwright-qa-cli'. Also triggered from /fix-ticket at pre-fix and post-fix stages. Works for any page or user flow — not limited to specific fea
Drupal Config Reconcile
84grasmash/drupal-claude-skills
Reconcile Drupal configuration drift between a working tree and a deployed environment one item at a time, deciding import (disk wins) vs export (DB wins) vs skip for each difference. Use when `drush config:status` shows drift, after pulling a fresh DB, before a deploy, or when local config and a remote/prod environment disagree. Pantheon/Terminus-aware but works with any remote alias; never writes to production.
Animated SVG
36omkamal/animated-diagrams-skill
This skill should be used when the user asks to "animate this diagram", "create an animated architecture diagram", "animated AWS/GCP/Azure diagram", "animated sequence diagram", "animated flowchart", "turn this PNG/SVG into an animation", "schematic animation", "data flow animation", "animate this SVG", "show the diagram style gallery", "illustrate a concept with cliparts/emojis", "animated concept illustration", "animate a large flow with pan and zoom", "code walkthrough animation", "Arabic animated diagram", "رسم متحرك", "animate this with my voiceover/SRT", "sync animation to narration time
Drupal Deploy Safety
84grasmash/drupal-claude-skills
Things that pass locally and then break, or silently lose data, on a Drupal deploy. Use when planning or running a deploy, writing a hook_update_N / post-update / deploy hook, running drush updb / updatedb / config:import / drush deploy on a remote environment, a site is stuck in maintenance mode after a failed or killed update, adding a column to a custom_field field, an update hook talks to an external API (payment provider, cloud, SaaS), changing a service constructor or *.services.yml / drush.services.yml arguments, a Drush command is missing from drush list, or committing vendor/ for a ho
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.