sentry-diagnose

Diagnose Sentry issues by fetching details and outlining cascading diagnostic workflows.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/onesmartguy/raptor-claude-plugins --skill sentry-diagnose
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sentry-diagnose
Source: https://github.com/onesmartguy/raptor-claude-plugins/tree/main/plugins/support-tools/skills/sentry-diagnose
Command: npx skills add https://github.com/onesmartguy/raptor-claude-plugins --skill sentry-diagnose

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose Sentry issues by fetching issue details, identifying the target project, and outlining a cascading diagnostic workflow that prioritizes logging steps before any destructive actions.

Core Features & Use Cases

  • Intelligent Sentry issue diagnosis: fetches issue details, determines the project (CPOMS or StaffSafe) from the issue's project field, and selects the relevant GitLab repository for scripts.
  • Script-guided root-cause analysis: analyzes the codebase to understand failure context, data flow, and model relationships to inform remediation.
  • Cascading workflow recommendations: proposes a sequence that starts with non-destructive logging scripts and, if applicable, follows with destructive scripts, or clearly states when no script applies.

Quick Start

Enter the Sentry issue URL to start the diagnosis workflow and receive recommended scripts.

Frequently Asked Questions about sentry-diagnose

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

FAQPage Schema
How do I diagnose a Sentry issue and find the relevant GitLab scripts for root-cause analysis?

To diagnose a Sentry issue, fetch the issue details, identify the target project (CPOMS or StaffSafe), and follow a cascading workflow that loads relevant GitLab scripts to pinpoint the root cause through structured logging steps.

What is the cascading diagnostic workflow for Sentry issues affecting multiple tenants?

A cascading diagnostic workflow for Sentry issues prioritizes non-destructive logging scripts first to gather data, then proceeds to destructive actions only when appropriate, ensuring safe root-cause analysis for multi-tenant environments.

How do I start root-cause analysis on a Sentry issue URL?

Enter the Sentry issue URL to initiate the diagnosis workflow. The system fetches issue details, determines the project from the issue's project field, and selects the relevant GitLab repository to propose a sequence of diagnostic scripts.

Do I need MCP servers and glab to run Sentry diagnostic scripts?

Yes, diagnosing Sentry issues requires MCP servers access, glab for GitLab interactions, and jq for JSON parsing. The workflow validates these prerequisites before running any diagnostic or destructive scripts.

When should I use destructive scripts for Sentry issue remediation?

Destructive scripts should only be used after non-destructive logging steps have been exhausted in the cascading workflow. The system clearly states when a destructive script applies or when no script fits the identified Sentry issue context.

Can I use sentry-diagnose for issues in projects other than CPOMS or StaffSafe?

Sentry-diagnose specifically identifies the target project from the issue's project field and loads scripts from CPOMS or StaffSafe repositories. It is designed for these specific project environments and their related GitLab scripts.