sentry-diagnose

Diagnose Sentry issues by analyzing codebase root causes and recommending remediation scripts.

Updated Jul 22, 2026
One-click install
npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill sentry-diagnose-trigent-software-pvt-ltd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sentry-diagnose
Source: https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc/tree/main/plugins/support-tools/skills/sentry-diagnose
Command: npx skills add https://github.com/Trigent-Software-Pvt-Ltd/trigen-aidlc --skill sentry-diagnose-trigent-software-pvt-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Support engineers investigating Sentry errors must manually correlate stacktraces with codebase logic and hunt through dozens of remediation scripts, which is slow and error-prone. This Skill automates that diagnosis by fetching the Sentry issue, analyzing the relevant GitLab codebase, and recommending a structured script workflow. ## Core Features & Use Cases - Automated Issue Analysis: Fetches Sentry issue details, stacktraces, and tenant tags via the Sentry MCP server, then assesses how many tenants are affected. - Codebase Root Cause Investigation: Uses an Explore agent to read the error location and trace data flow in the CPOMS or StaffSafe GitLab repositories. - Cascading Script Recommendations: Matches errors against 120+ GitLab-hosted scripts, distinguishing logging scripts from destructive scripts, and enriches recommendations with Confluence gotchas. - Use Case: A support engineer receives a Sentry alert about duplicate medical condition records for one school. The Skill identifies the tenant, confirms the issue is isolated, and recommends running a logging script first, then a dedupe script with dry-run enabled in Manage. ## Quick Start Diagnose the Sentry issue at this URL and recommend which scripts to run for the affected customer.

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 root cause?

Provide the Sentry issue URL and the Skill fetches error details, stacktrace, and tenant tags via the Sentry MCP server. It then explores the matching GitLab codebase to trace the data flow and explain the root cause before recommending next steps.

How do I find the right remediation script for a Sentry error?

The Skill lists all scripts from the target project's GitLab repository and matches them to the error pattern by name and model. It distinguishes logging scripts, which gather IDs and state, from destructive scripts, which modify data, and recommends running logging first.

What tools are required to run Sentry issue diagnosis?

You need the Sentry and Atlassian MCP servers configured in Claude Code, plus the glab CLI authenticated with GitLab and the jq JSON processor installed. The Skill checks for glab and jq before starting and reports MCP errors when tools are first called.

Does the diagnosis support multiple projects or repositories?

Yes, the Sentry issue's projectID determines the target: project 152386 maps to CPOMS and 1271707 maps to StaffSafe, each with its own GitLab repository. Only the relevant project's scripts and codebase are loaded.

What happens when no script can fix a Sentry error?

The Skill explicitly states that no script applies and explains why, such as when the error is a code defect with no corrupted data. It then recommends customer workarounds, escalation paths, and Jira tickets for the underlying fix.

Why should destructive scripts be dry-run first?

Destructive scripts modify customer data, so running them with dry-run enabled first lets you verify the affected records before committing changes. Scripts inheriting from Scripts::DryRun support this mode, and the Skill flags dry-run support in every recommendation.