Incident Pattern Matcher

incident-pattern-matcher

A Claude Code skill for SREs and engineering teams to identify recurring failure patterns across post-mortems and incident logs.

[](https://github.com/posit-dev/incident-pattern-matcher) [](https://github.com/posit-dev/claude-plugins)

---

What it does

The **Incident Pattern Matcher** skill lets you query across all your historical post-mortems and incident logs to surface recurring root causes, reliability trends, and engineering focus areas — without manually trawling through Confluence pages and Slack threads.

It connects live to:

• 📄 Confluence — post-mortem pages across PTD, HOS, and Platform spaces
• 💬 Slack — #hosted-incidents and per-incident channels (e.g. created by Datadog)
• 🎫 Jira — incident tickets for cross-referencing

---

Trigger phrases

Use these in Claude to activate the skill:

Have we seen a failure like this before?
Generate a summary of our reliability trends this quarter.
Which service has the most recurring incidents?
Where should we focus engineering mop-up time?
What are the top root causes across all post-mortems?

---

What Claude returns

Every analysis is structured as:

Section	Description
Pattern Summary	Concise headline of the finding
Recurring Patterns	Grouped failure modes with frequency
Root Cause Analysis	Why these patterns keep recurring
Recommended Focus Areas	Where to invest engineering time
Trend Outlook	Improving, worsening, or new pattern?

---

Installation

1. Add to your Claude project

In your Claude project settings, add this skill from the [Posit Plugin Marketplace](https://github.com/posit-dev/claude-plugins).

2. Required MCP integrations

This skill requires the following MCP servers to be connected in your