router

Classify incidents into predefined categories and route them in a diagnostic pipeline.

1|Updated Mar 7, 2026

Search Tags:#automation #error handling #log analysis #diagnosis #incident classification #pipeline routing

Ready to run

npx skills add https://github.com/jimmymalhan/codereview-pilot --skill router-jimmymalhan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: router
Source: https://github.com/jimmymalhan/codereview-pilot/tree/main/.claude/skills/router
Command: npx skills add https://github.com/jimmymalhan/codereview-pilot --skill router-jimmymalhan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the classification and routing of incidents, ensuring that each request is correctly handled by the appropriate stage in the diagnosis pipeline.

Core Features & Use Cases

Incident Classification: Categorizes incidents into predefined types such as Resource Contention, Memory Leak, Config Error, DNS, Concurrency, and Deployment.
Pipeline Routing: Directs classified incidents to the next stage in the diagnostic process based on their type.
Use Case: When a new incident report comes in, this Skill will automatically determine if it's a memory leak or a configuration error, and then pass it to the correct module for detailed analysis.

Quick Start

Use the router skill to classify the incident "Database query takes 45 seconds, CPU 100% on replicas".

Frequently Asked Questions about router

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

FAQPage Schema

How do I automate incident classification for a diagnostic pipeline?▼

Automated incident classification categorizes incoming issues into predefined types like Resource Contention or Memory Leak. It maps incident symptoms to established categories, providing a confidence score and rationale to ensure accurate routing within a diagnostic pipeline.

What types of incidents can be automatically routed during log analysis?▼

Incident routing handles symptom analysis for several distinct categories: Resource Contention, Memory Leak, Config Error, DNS, Concurrency, and Deployment. This ensures each incident is directed to the appropriate stage for detailed diagnosis.

How does incident classification determine the correct routing path?▼

Incident classification determines routing by analyzing the symptoms of an incoming report and mapping them to established categories. It then provides a confidence score with rationale to justify the selected diagnostic path.

Can I use automated routing for deployment errors and concurrency issues?▼

Yes, automated routing explicitly handles both Deployment and Concurrency incidents. The classification process analyzes the symptoms of these errors to map them to the correct category for further diagnostic analysis.

What is the best way to route resource contention and memory leak incidents?▼

The best way to route resource contention and memory leak incidents is through automated symptom analysis. This process maps the specific symptoms to predefined categories, passing the incident to the correct module for detailed analysis.