sentry-analyze

Analyzes Sentry issues across five dimensions, classifies severity, and checks Jira for existing tickets.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Triaging Sentry errors manually requires digging through stacktraces, tags, releases, and Jira to decide severity and next steps. This Skill automates that deep analysis so engineers get a structured triage report and a clear action choice without re-fetching data. ## Core Features & Use Cases - Five-Dimension Analysis: Evaluates trigger source, impact, error patterns, infrastructure context, and related Sentry issues using gathered context and Sentry MCP tools. - Severity Classification: Applies a CRITICAL/HIGH/MEDIUM/LOW rubric based on user impact, exception handling, and release correlation. - Jira Duplicate Detection: Searches Jira via acli or Atlassian MCP for existing tickets before recommending actions, and probes sentry-cli availability for downstream automation. - Use Case: After running /sentry-triage on a production NoMethodError affecting 45 users, this Skill correlates the issue with release v2.3.1, finds no existing Jira ticket, classifies it HIGH, and presents Archive, Jira, or Slack escalation options. ## Quick Start Ask the assistant to analyze the Sentry issue context passed from /sentry-triage and classify its severity with recommended triage actions.

Frequently Asked Questions about sentry-analyze

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

FAQPage Schema
How do I analyze a Sentry issue and classify its severity?

Invoke this skill with the YAML context from /sentry-triage or provide issue details directly. It evaluates trigger source, impact, error patterns, infrastructure, and related issues, then assigns CRITICAL, HIGH, MEDIUM, or LOW severity using a defined rubric.

How does the skill check for existing Jira tickets?

It first probes Jira availability, preferring the acli CLI and falling back to Atlassian MCP tools. It then runs JQL text searches using the Sentry issue ID, error keywords, and error class name to find matching tickets.

Does the Sentry analysis work without the Sentry MCP tools?

The skill primarily uses Sentry MCP tools like search_issues and get_issue_details, with alternate mcp__sentry__ prefixes as fallback. It works from the context block gathered by /sentry-triage and only makes additional calls when data is insufficient.

What happens if Jira is unavailable during triage?

If both acli and Atlassian MCP fail, the skill sets jira_mode to unavailable, skips the duplicate ticket search, and continues with analysis and severity classification. The Jira action option is then omitted from the action selection prompt.

What actions can I take after the Sentry analysis completes?

You can choose to Archive the issue, create or link a Jira ticket, send it to Automaton, escalate to Slack, or request more diagnostic context. The chosen action is forwarded with full context to the /sentry-action skill for execution.