incident-alert-tickets

List Linear issues carrying the incident-alert label, then match on the monitor ID stored in the ticket's alert header, falling back to monitor title and environment. Read the matched ticket's dated cause sections and comments for documented recognition signals and fixes.

Propose a dated cause section with Recognize it, How urgent, and Fix fields, presented in an approval table first. Only after explicit human approval is the section appended above the ticket's Your cause is not listed trailer.

No, all writes are gated on explicit human approval. The skill presents a proposal table with classification, proposed action, and draft content, then waits for the human to select rows before creating or appending anything.

Each alert identity gets its own lookup, comparison, and classification because every monitor has its own ticket. If one root cause explains several alerts, the full cause section goes on the monitor closest to the cause, with short linking sections proposed on the others.

Skip it when there is no alert identity, such as a customer report or general code question with no named Datadog monitor, incident.io alert, or on-call page. The presence of a named alert is the mandatory trigger condition.