Automated Incident Triage & Resolution FAQs

Question 1

Do I need the Sentry MCP to use this skill?

Accepted Answer

The skill is optimized for the Sentry MCP (Model Context Protocol) for deep AI-assisted analysis, but it can also function using the standard Sentry CLI and environment variables.

Question 2

How does the postmortem feature work?

Accepted Answer

Once a fix is merged and deployed, the skill verifies that the errors have stopped in production, generates a postmortem document based on the incident context, and resolves the issue in Sentry.

Question 3

Can this skill automatically fix my production bugs?

Accepted Answer

It automates the investigation and PR creation phases. It identifies the root cause, creates a fix branch, loads the relevant code, and prepares the PR, though it requires developer oversight for final logic validation.

Question 4

Does it support GitHub Actions debugging?

Accepted Answer

Yes, the 'investigate-ci' command fetches failed workflow logs via the GitHub CLI, identifies the specific failing step, and helps resolve type errors, linting violations, or broken tests.

Question 5

What observability sources does the Triage skill monitor?

Accepted Answer

The skill monitors Sentry for application errors, Vercel for server logs, GitHub Actions for CI/CD workflow status, and custom /api/health endpoints for system uptime.

Automated Incident Triage & Resolution

Automated Incident Triage & Resolution

Key Features

Use Cases

Key Features

Use Cases