stacktrace-log-triage

Name: stacktrace-log-triage
Availability: InStock
Author: JetBrains

Diagnose Kotlin and Spring failures from stack traces and logs.

302|22|Updated Feb 12, 2026

Search Tags:#kotlin #diagnose #triage #spring #root-cause #stack-trace

Ready to run

npx skills add https://github.com/JetBrains/skills --skill stacktrace-log-triage-jetbrains

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: stacktrace-log-triage
Source: https://github.com/JetBrains/skills/tree/main/stacktrace-log-triage
Command: npx skills add https://github.com/JetBrains/skills --skill stacktrace-log-triage-jetbrains

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose Kotlin + Spring failures from stack traces, startup logs, runtime logs, and related metrics, then separate root cause from wrapper exceptions and propose safe next steps.

Core Features & Use Cases

Triage failures by tracing the Caused by chain and surrounding context to identify the most informative root cause.
Distinguish symptom, proximate cause, and true root cause; provide a ranked list of hypotheses with confidence levels.
Propose safe mitigations (hotfix) and a long-term fix, including steps to verify in testing and monitoring.
Works with logs, traces, and correlation data to guide remediation during startup failures, endpoint crashes, or degraded services.

Quick Start

Diagnose Kotlin + Spring failures by analyzing a stack trace and related logs to yield a prioritized root-cause diagnosis and recommended next steps.

Frequently Asked Questions about stacktrace-log-triage

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

FAQPage Schema

How do I diagnose Kotlin Spring failures from a stack trace?▼

Triage a Kotlin Spring startup failure by analyzing the stack trace and related logs to distinguish the true root cause from wrapper exceptions, providing a ranked list of hypotheses with confidence levels and safe mitigation steps.

Why does my Spring application crash on endpoint requests and how do I find the root cause?▼

Find the root cause of an endpoint crash by tracing the stack trace and correlation identifiers across runtime logs to separate the proximate cause from the symptom, providing structured output with hotfix and long-term fix recommendations.

Can I use a stack trace to separate root causes from wrapper exceptions in Spring?▼

Yes, you can separate root causes from wrapper exceptions by tracing the Caused By chain and surrounding context within the stack trace to distinguish the symptom, proximate cause, and true root cause of the Spring failure.

What is the best way to triage noisy Spring runtime logs and nested exceptions?▼

Triage noisy Spring runtime logs by analyzing nested exceptions and related metrics to identify the most informative root cause, providing structured output including evidence, hotfix, long-term fix, and verification steps.

Does this root-cause diagnosis approach work with Kotlin and Spring startup failures?▼

Yes, this root-cause diagnosis approach works with Kotlin and Spring startup failures by applying stack trace analysis, runtime logs, and related metrics to guide remediation during degraded services or startup crashes.