skills.rest
kbrgnj
kbrgnjCOMMUNITY
Explore all skills by this author →
GitHub

stacktrace-log-triage

Diagnose Kotlin and Spring failures from stack traces and logs.

14|1|Updated Mar 6, 2026
Search Tags:#diagnosis#kotlin#spring#root-cause#log-triage#stacktrace
One-click install
npx skills add https://github.com/kbrgnj/kotlin-backend-agent-skills --skill stacktrace-log-triage-kbrgnj
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stacktrace-log-triage
Source: https://github.com/kbrgnj/kotlin-backend-agent-skills/tree/main/.agents/skills/stacktrace-log-triage
Command: npx skills add https://github.com/kbrgnj/kotlin-backend-agent-skills --skill stacktrace-log-triage-kbrgnj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose Kotlin + Spring failures from stack traces, startup logs, runtime logs, and related metric anomalies, then separate root cause from wrapper exceptions and propose safe next steps. Use when the application fails to start, an endpoint crashes, logs are noisy or deeply nested, or the agent must produce both a quick mitigation and a proper long-term fix without guessing.

Core Features & Use Cases

  • Turn noisy failure evidence into a ranked diagnosis with explicit confidence.
  • Always distinguish symptom, proximate cause, and true root cause.

Quick Start

Provide a full stack trace, relevant logs, and context to the agent and request a triage diagnosis with recommended mitigations.

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 a Kotlin Spring startup failure from a stack trace?▼

Diagnose Kotlin Spring startup failures by providing the full stack trace and startup logs to separate root causes from wrapper exceptions, yielding ranked diagnoses with quick mitigations and long-term fixes.

What is the best way to find the root cause of deeply nested Spring exceptions?▼

The best way to find the root cause of nested Spring exceptions is through causal chain analysis, which explicitly separates the initial symptom from the proximate cause and the true root cause.

Why does my Kotlin Spring endpoint crash without a clear error message?▼

Kotlin Spring endpoints often crash without clear messages due to wrapper exceptions masking the true error; structured evidence gathering and log triage identify the hidden root cause.

Can I get both quick mitigations and long-term fixes for noisy Kotlin application logs?▼

Yes, you can get both quick mitigations and long-term fixes for noisy Kotlin logs by analyzing the stack traces and runtime anomalies to produce safe, actionable next steps.

What should I provide to triage crashing Spring endpoints and metric anomalies?▼

To triage crashing Spring endpoints and metric anomalies, you should provide the full stack trace, relevant runtime logs, and application context to generate a structured diagnosis.

Related Skills

Explore More Software Engineering Skills→
JetBrainsJetBrains
302

stacktrace-log-triage

Diagnose Kotlin and Spring failures from stack traces and logs.

Official
Advanced
KotlinKotlin
14

stacktrace-log-triage

Identify root causes of Kotlin and Spring failures from stack traces and logs.

Official
Advanced
Mekann2904Mekann2904

log-analyzer

Analyze log files to extract error patterns and detect anomalies.

Community
Intermediate
mymx2mymx2
4

stacktrace-log-triage

Diagnose Kotlin and Spring failures by analyzing stack traces and startup logs.

Community
Advanced