skills.rest
aaronbrethorst
aaronbrethorstCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

investigate-sentry

Investigate Sentry production errors and apply TDD fixes.

5|Updated Jan 31, 2026
Search Tags:#tdd#debugging#sentry#production support#rails#error fixing
One-click install
npx skills add https://github.com/aaronbrethorst/claude-skills --skill investigate-sentry
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: investigate-sentry
Source: https://github.com/aaronbrethorst/claude-skills/tree/main/investigate-sentry
Command: npx skills add https://github.com/aaronbrethorst/claude-skills --skill investigate-sentry

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of investigating and fixing production errors reported in Sentry, reducing downtime and developer effort.

Core Features & Use Cases

  • Automated Error Analysis: Fetches full Sentry issue data, analyzes root causes, and scores fix confidence.
  • TDD-Based Fixing: Applies a Test-Driven Development approach to ensure fixes are robust and regressions are prevented.
  • Use Case: When a critical bug is reported in Sentry with an ID like PROJ-123, this Skill can automatically analyze the issue, propose a fix, write a failing test case, and implement the solution.

Quick Start

Use the investigate-sentry skill to fix the Sentry issue VOTERLETTERS-9R.

Frequently Asked Questions about investigate-sentry

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix production errors from Sentry using a TDD approach?▼

Fix production errors from Sentry by fetching full issue data via the Sentry MCP, analyzing the root cause, and writing a failing spec from the Sentry data before implementing the code fix to ensure robust regression prevention.

Can I automatically analyze Sentry issues and score fix confidence before applying changes?▼

Yes, analyzing Sentry issues includes scoring fix confidence across three dimensions. Based on the confidence score, the workflow branches into a plan-only, plan-then-fix, or auto-fix strategy before applying any Test-Driven Development changes.

How do I prevent regressions when debugging Rails production support issues?▼

Prevent regressions during Rails production support by applying a TDD red-to-green workflow: generate a failing test case directly from the Sentry error data, then implement the code fix until the test passes.

Does this Sentry error fixing workflow require manual intervention for every issue?▼

No, Sentry error fixing can branch into an auto-fix mode based on high confidence scores. For lower confidence issues, it generates a plan-only or plan-then-fix approach, minimizing unnecessary manual intervention while ensuring safety.

What is the best way to investigate a Sentry issue ID like PROJ-123?▼

Investigate a Sentry issue like PROJ-123 by fetching its full data through the Sentry MCP, analyzing the root cause automatically, and writing a failing spec from that data to guide the Test-Driven Development fix.

Related Skills

Explore More Software Engineering Skills→
MadBomberMadBomber
11

RSpec Testing

Generate and debug RSpec unit and integration tests for Ruby and Rails.

Community
Advanced
ginkidaginkida
20

sentry

Instrument production errors with Sentry SDK integration and release tagging.

Community
Intermediate
MrlykMrlyk
4

test-driven-development

Enforce failing tests before implementation with per-repo test commands and trace.jsonl logging.

Community
Intermediate
huynguyenhhuynguyenh
3

hnh-report-sentry

Fetch Sentry issue context and analyze local codebase for root causes.

Community
Advanced