Spring Context Di Reasoning

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.

398 stars 35 forksMobile Development

Install

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

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

From the SKILL.md

# Spring Context DI Reasoning

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

## Mission

Reconstruct why the Spring container made a specific decision and propose the narrowest fix that restores correct wiring.
Assume the visible exception is often a wrapper, not the real cause.

## Collect Evidence First

- Read the full exception chain, not only the top exception.
- Read the startup log lines around the first failure and around any `Caused by:` entries.
- Read the relevant `@Configuration`, component classes, `@Bean` methods, `@ConfigurationProperties`, and active profiles.
- Read the build context if it is not already known. Reuse output from `project-context-ingestion` when available.
- If a condition evaluation report or auto-configuration report exists, use it.

## Reconstruct The Bean Path

- Identify the bean that failed first.
- Walk constructor arguments, method parameters, and factory methods to build the dependency chain.
- Separate symptom from cause:
  - `BeanCreationException` is usually a wrapper.
  - `UnsatisfiedDependencyException` usually points to a missing or ambiguous dependency one hop deeper.
  - property binding failures often surface as bean creation failures.
- Record whether the failing bean is user-defined, auto-configured, conditional, profile-specific, or imported from another module.

## Diagnose By Category

Check these categories in order:

1. Missing bean:
   - package not scanned
Read the full skill on GitHub

Details

Skill name
spring-context-di-reasoning
Path
spring-context-di-reasoning/SKILL.md
Repo updated
21 October 2026

FAQ

What does the Spring Context Di Reasoning skill do?

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.

How do I install the Spring Context Di Reasoning skill?

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

Is Spring Context Di Reasoning 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

Stacktrace Log Triage

398

JetBrains/skills

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.

Mobile Development35

Project Context Ingestion

398

JetBrains/skills

Inspect a Kotlin + Spring repository before making changes or answering implementation, debugging, build, architecture, or review questions. Use when the agent must map modules, Spring Boot/Kotlin/Gradle/JDK versions, compiler plugins, profiles, dependencies, runtime stack, and architectural boundaries so later advice stays compatible with the real project.

Mobile Development35

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

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