Sentry Fix Issues
技能 已验证 活跃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.
To provide developers with an AI-driven workflow for efficiently resolving production issues surfaced in Sentry, reducing debugging time and improving application stability.
功能
- 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 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.
非目标
- 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.
工作流
- 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
实践
- Security constraints
- Code validation
- Root cause analysis
- Testing
先决条件
- Sentry MCP server configured and connected
- Access to the Sentry project/organization
安装
请先添加 Marketplace
/plugin marketplace add getsentry/sentry-for-ai/plugin install sentry-for-ai@sentry-plugin-marketplace质量评分
已验证类似扩展
Node Connect
100Diagnose OpenClaw Android, iOS, or macOS node pairing, QR/setup code, route, auth, and connection failures.
Openclaw Debugging
100Debug OpenClaw model, provider, tool-surface, code-mode, streaming, and live/Crabbox behavior by choosing the right logs, probes, and proof path before changing code.
Systematic Debugging
100Systematic debugging methodology emphasizing root cause analysis over quick fixes
Troubleshooting
100使用 Chrome DevTools MCP 和文档来排查连接和目标问题。当 list_pages、new_page 或 navigate_page 失败，或服务器初始化失败时，触发此技能。
Root Cause Tracing
99Use 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
Query Agent Events
99Bug-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.