Incident Triage

Gather Sentry and Axiom error context via MCP and map it to tasks and specifications for remediation planning.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/samhmariam/caritas-agent-control-plane --skill incident-triage-samhmariam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Incident Triage
Source: https://github.com/samhmariam/caritas-agent-control-plane/tree/main/.agents/skills/incident-triage
Command: npx skills add https://github.com/samhmariam/caritas-agent-control-plane --skill incident-triage-samhmariam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Incident triage automates gathering context from observability tools, maps it to related tasks, and guides teams toward constitutional-compliant fixes while updating documentation.

Core Features & Use Cases

  • Context gathering: Pulls logs and errors from Sentry and Axiom via MCP and correlates with AGENTS.md-guided processes.
  • Task mapping: Links incidents to tasks and specifications to streamline remediation and approvals.
  • Documentation update: Proposes incident notes and runbooks for post-mortems and audits.
  • Use Case: During a production outage, the skill surface tracks the event timeline, aligns with tasks, and generates a remediation plan.

Quick Start

Invoke the incident-triage workflow to investigate a given Sentry issue and assemble logs, tasks, and fixes.

Frequently Asked Questions about Incident Triage

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

FAQPage Schema
How do I automate incident triage with Sentry and Axiom logs?

Automating incident triage involves pulling Sentry errors and Axiom logs via MCP, correlating them with related tasks and specifications to reconstruct event timelines, and generating a structured remediation plan for rapid resolution.

What is the best way to map production errors to source code and requirements?

Mapping production errors to source code and requirements is done by correlating observability data with AGENTS.md-guided processes, linking incidents directly to task identifiers (TXXX) and specifications (FR-XXX) to streamline approvals and remediation.

Can I generate post-mortem documentation from Sentry issues and Axiom logs?

Generating post-mortem documentation from Sentry issues and Axiom logs is supported by proposing structured incident notes and runbooks that align event timelines with tasks and constitutional principles for audits.

Does incident triage work without configuring dependencies?

Incident triage operates with no listed dependencies, requiring only MCP connectivity to Sentry and Axiom to gather error context and map it directly to source code, tasks, and requirements.

Why should I use automated triage for production outages instead of manual log analysis?

Automated triage for production outages accelerates resolution by reconstructing event timelines and proposing fixes that adhere to constitutional principles, replacing manual log correlation with structured remediation plans.

How do I investigate a Sentry issue and assemble logs and fixes for incident response?

Investigating a Sentry issue and assembling logs requires invoking the incident-triage workflow, which surfaces the event timeline, aligns with related tasks, and generates a comprehensive remediation plan.