Stacktrace Log Triage

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.

398 stars 35 forksMobile Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add JetBrains/skills --skill stacktrace-log-triage
Manual install
git clone --depth 1 https://github.com/JetBrains/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/stacktrace-log-triage ~/.claude/skills/stacktrace-log-triage

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Stacktrace Log Triage

Source mapping: Tier 1 critical skill derived from `Kotlin_Spring_Developer_Pipeline.md` (`SK-15`).

## Mission

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

## Gather Evidence First

- Read the full stack trace, not only the top frame.
- Read the surrounding log lines before and after the first failure.
- Capture timestamps, correlation ids, request ids, thread names, and active profiles when available.
- Read recent relevant code or config changes if they are available.
- Reuse repository constraints from `project-context-ingestion` when possible.

## Triage Workflow

1. Find the earliest meaningful failure signal.
2. Walk the `Caused by:` chain until it stops getting more specific.
3. Classify the incident:
   - DI and context startup
   - configuration binding
   - serialization or validation
   - SQL or migration
   - HTTP or timeout
   - security
   - concurrency or locking
   - classpath or version mismatch
4. Separate what failed from why it failed.
5. Rank hypotheses when evidence is incomplete.
6. Propose a quick mitigation and a proper fix separately.

## Diagnostic Rules

- Treat `BeanCreationException`, `InvocationTargetException`, and similar wrappers as transport, not diagnosis.
- Treat the first user-code frame after framework wrappers as high-signal evidence.
- Use log chronology, not stack depth alone.
Read the full skill on GitHub

Details

Skill name
stacktrace-log-triage
Path
stacktrace-log-triage/SKILL.md
Repo updated
21 October 2026

FAQ

What does the Stacktrace Log Triage skill do?

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.

How do I install the Stacktrace Log Triage skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add JetBrains/skills --skill stacktrace-log-triage. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Stacktrace Log Triage popular?

It lives in JetBrains/skills, which has 398 GitHub stars and 35 forks.

Related skills

Deploy to Vercel

398

JetBrains/skills

Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".

DevOps & CloudIn 2 lists35

Vercel React Native Skills

398

JetBrains/skills

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

Mobile DevelopmentIn 2 lists35

Vitest

398

JetBrains/skills

Vitest fast unit testing framework powered by Vite with Jest-compatible API. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.

Testing & QA35

Sim Use

260

cafe3310/public-agent-skills

Drive iOS Simulator and Android emulator/device screens for AI agents. Use when asked to automate a simulator or emulator, tap/swipe/type on a device, describe UI, take a screenshot, or interact with a mobile app.

Mobile Development30

Spring Context Di Reasoning

398

JetBrains/skills

Diagnose Spring application context startup failures, bean graph problems, missing or duplicate beans, circular dependencies, conditional auto-configuration mismatches, and profile-related wiring issues in Kotlin + Spring projects. Use when the app does not start, a bean is not created or is created unexpectedly, auto-configuration behaves strangely, or a minimal DI fix is needed instead of a broad rewrite.

Mobile Development35

Flutter API

192

smallnest/goskills

Comprehensive Flutter API reference guide covering widgets, Material Design, Cupertino, animations, gestures, navigation, state management, and platform integration. Use when developing Flutter applications and needing detailed API knowledge for widgets, layout, styling, animations, platform channels, or any Flutter SDK functionality. Essential for building cross-platform mobile, web, and desktop applications with Flutter.

Mobile Development27

Browse the most popular Claude skills, all mobile development skills, or write your own with the skills generator.