incidents-to-rule

Analyze incident drafts and audits to generate AGENTS.md rule candidates.

1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/JayJihyunKim/rein --skill incidents-to-rule
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: incidents-to-rule
Source: https://github.com/JayJihyunKim/rein/tree/main/plugins/rein-core/skills/incidents-to-rule
Command: npx skills add https://github.com/JayJihyunKim/rein --skill incidents-to-rule

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze trail/incidents to generate candidate rules for AGENTS.md.

Core Features & Use Cases

  • Automated incident analysis: reviews trail/incidents/ entries and derives actionable rule candidates for AGENTS.md.
  • Decision tracking: records suggested rules along with context to guide reviewer decisions for escalation.
  • Scope and triggers: supports incident drafts, daily audits, and manual requests for latest incidents.

Quick Start

Review the latest incidents and run the analysis to propose AGENTS.md rule candidates.

Frequently Asked Questions about incidents-to-rule

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

FAQPage Schema
How do I turn incident trails into AGENTS.md rules automatically?

You can generate AGENTS.md rule candidates by analyzing incident trail entries to derive actionable rules, recording suggested rules with context to guide reviewer decisions for escalation.

What is the process for analyzing recent incidents to propose AGENTS.md rule candidates?

Incident analysis reviews trail/incidents entries and incident drafts to produce structured rule candidates, updating incident metadata with agent eligibility and root-cause classifications to guide rule escalation.

Can I use incident drafts and daily audits for rules generation?

Yes, rules generation supports incident drafts, daily audits, and manual requests for latest incidents, producing structured rule candidates and updating incident metadata with frontmatter structure and status tracking.

How does incident metadata tracking work during rules generation?

Incident metadata tracking enforces frontmatter structure and tracks statuses via auto-*.md files, recording agent eligibility and root-cause classifications to guide rule escalation decisions.

What is the best way to manage rule escalation from incident trails?

The best way to manage rule escalation is to analyze incident trails to generate structured rule candidates, recording context and root-cause classifications that guide reviewer decisions for escalation.

Do I need specific dependencies to run incident analysis for AGENTS.md rules?

No specific dependencies are required to run incident analysis for AGENTS.md rules, as the skill operates independently to review incident trails and generate structured rule candidates with metadata tracking.