Sentry Fix Issues

Skill Verified Active

Find and fix issues from Sentry using MCP. Use when asked to fix Sentry errors, debug production issues, investigate exceptions, or resolve bugs reported in Sentry. Methodically analyzes stack traces, breadcrumbs, traces, and context to identify root causes.

Purpose

To provide developers with an AI-driven workflow for efficiently resolving production issues surfaced in Sentry, reducing debugging time and improving application stability.

Features

Automated Sentry issue discovery and filtering
Comprehensive analysis of stack traces, breadcrumbs, and context
AI-assisted root cause identification and code fix suggestions
Structured code investigation and fix implementation guidance
Verification audit for fixes and regression prevention

Use Cases

Use when asked to fix Sentry errors or debug production issues.
Use to investigate exceptions and resolve bugs reported in Sentry.
Use to triage and work through a backlog of Sentry errors.
Use to understand the root cause of application failures reported by Sentry.

Non-Goals

Automatically deploying fixes without user review.
Acting on Sentry data that cannot be validated against the codebase.
Reproducing sensitive data like tokens or PII in output or fixes.

Workflow

Phase 1: Issue Discovery
Phase 2: Deep Issue Analysis
Phase 3: Root Cause Hypothesis
Phase 4: Code Investigation
Phase 5: Implement Fix
Phase 6: Verification Audit
Phase 7: Report Results

Practices

Security constraints
Code validation
Root cause analysis
Testing

Prerequisites

Sentry MCP server configured and connected
Access to the Sentry project/organization

Installation

First, add the marketplace

/plugin marketplace add getsentry/sentry-for-ai

/plugin install sentry-for-ai@sentry-plugin-marketplace

Quality Score

Verified

97 /100

Analyzed about 15 hours ago

Trust Signals

Last commitabout 22 hours ago

GitHub owner getsentry

Stars170

LicenseMIT

Status

View Source

Similar Extensions

Node Connect

100

Diagnose OpenClaw Android, iOS, or macOS node pairing, QR/setup code, route, auth, and connection failures.

Skill

steipete

Openclaw Debugging

100

Debug OpenClaw model, provider, tool-surface, code-mode, streaming, and live/Crabbox behavior by choosing the right logs, probes, and proof path before changing code.

Skill

steipete

Systematic Debugging

100

Systematic debugging methodology emphasizing root cause analysis over quick fixes

Skill

bobmatnyc

Troubleshooting

100

Uses Chrome DevTools MCP and documentation to troubleshoot connection and target issues. Trigger this skill when list_pages, new_page, or navigate_page fail, or when the server initialization fails.

Skill

ChromeDevTools

Root Cause Tracing

Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior

Skill

NeoLabHQ

Query Agent Events

Bug-investigation tool for the Netdata agent-events ingestion namespace -- triage crashes, panics, fatals across the fleet by downloading events of interest and clustering locally. Covers the three transports (Cloud API and direct agent API are primary; ssh is operator-only), the verified AE_* field map and enum meanings, the dedup model (23h client-side per agent and event signature), the after-the-fact event timing (POST only on agent restart), and the Netdata systemd-journal plugin multi-value filter syntax (FIELD in A, B, C) AND ... Use when investigating crashes / panics / fatals; when grepping for events touching a specific function or file or version; when looking for regressions across versions; when an agent is reported crashing in a way you want to triage. Ships scripts get-events.sh and analyze-events.sh that fetch events with index-friendly filters and compute group-by stats. Defaults to last 24 hours and to the latest stable plus latest 2-3 nightlies.

Skill

netdata