error-triage

Classify Sentry production errors by severity and root cause.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Vincri126/MCO-Template --skill error-triage-vincri126
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error-triage
Source: https://github.com/Vincri126/MCO-Template/tree/main/.orchestrator/skills/error-triage
Command: npx skills add https://github.com/Vincri126/MCO-Template --skill error-triage-vincri126

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It keeps production errors from overwhelming teams by transforming noisy Sentry issues into prioritized, actionable guidance and ensuring fixes are routed with context and accountability.

Core Features & Use Cases

  • Structured Triage Protocol: Fetch issues, events, and traces from Sentry, classify by severity, and log actions in PROJECT_STATUS.json so stakeholders know what is happening with every incident.
  • Root Cause & Fix Recommendations: Diagnose errors via stack traces, deployment correlations, and error categories, then craft fix summaries with severity, frequency, and verification instructions for rapid handoff.
  • Degraded Mode Resilience: Detect missing telemetry tools, announce degraded mode, mark unverifiable findings, and continue triage using pasted logs while recording the fallback in the action log.
  • Cross-Skill Integration: Escalate critical bugs through qa-gate, link issues to project tracker entries, compare deployments with vercel-deploy, and surface regression tests via testing-cicd and version-logger.

Quick Start

Use the error-triage skill to fetch recent Sentry issues, assign severity, and report recommended fixes.

Frequently Asked Questions about error-triage

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

FAQPage Schema
How do I triage Sentry production errors and classify them by severity?

To triage Sentry production errors, the skill fetches Sentry issues, events, and trace details, then classifies each by severity and root cause. It logs triage actions in PROJECT_STATUS.json so stakeholders can track every incident's status and recommended fix.

What's the best way to find the root cause of a Sentry outage using stack traces?

Finding the root cause of a Sentry outage involves analyzing stack traces, deployment correlations, and error categories. The skill diagnoses errors from these telemetry sources and crafts fix summaries with severity, frequency, and verification instructions for rapid handoff.

Can I still run incident triage if my Sentry telemetry tools are missing or inaccessible?

Yes, incident triage works in degraded mode when telemetry tools are missing. The skill announces degraded mode, marks unverifiable findings, continues triage using pasted logs, and records the fallback approach in the action log for full transparency.

How do I prioritize bugs from Sentry issues during a production incident?

Bug prioritization from Sentry issues is handled by fetching recent errors, assigning severity based on incident impact, and generating structured fix recommendations. The skill ensures every prioritized bug includes context and accountability for routing to the correct team.

Does this Sentry error triage workflow integrate with deployment tracking and QA gates?

Yes, the Sentry error triage workflow integrates cross-skill by escalating critical bugs through qa-gate, comparing deployments with vercel-deploy, and surfacing regression tests via testing-cicd and version-logger to ensure comprehensive incident resolution.