dependency-conflict-resolver

Diagnose Gradle and Spring classpath conflicts in Kotlin applications.

14|1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/kbrgnj/kotlin-backend-agent-skills --skill dependency-conflict-resolver-kbrgnj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependency-conflict-resolver
Source: https://github.com/kbrgnj/kotlin-backend-agent-skills/tree/main/.agents/skills/dependency-conflict-resolver
Command: npx skills add https://github.com/kbrgnj/kotlin-backend-agent-skills --skill dependency-conflict-resolver-kbrgnj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose and resolve Gradle and Spring classpath conflicts in Kotlin applications to keep builds healthy and predictable.

Core Features & Use Cases

  • Identify conflicting versions across modules, BOMs, catalogs, and dependency graphs.
  • Determine the winning version and the authority responsible for the final decision.
  • Propose minimal, safe fixes and provide verification steps to ensure no regressions.

Quick Start

Run dependency-conflict-resolver against your Kotlin/Spring project to identify the root cause and propose a minimal, non-invasive fix.

Frequently Asked Questions about dependency-conflict-resolver

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

FAQPage Schema
How do I resolve a NoSuchMethodError caused by Gradle dependency conflicts in Kotlin?

To resolve a NoSuchMethodError from Gradle dependency conflicts in Kotlin, identify the winning artifact and owning authority across BOMs and catalogs, then apply a minimal safe fix with verification steps to prevent regressions.

Why does my Spring application throw a ClassNotFoundException or NoClassDefFoundError during build?

A Spring application throws a ClassNotFoundException or NoClassDefFoundError due to version drift across Gradle dependency graphs. Diagnose the classpath conflicts to determine the winning version and correct the dependency authority.

What is the best way to find the winning version in a Gradle dependency graph?

The best way to find the winning version in a Gradle dependency graph is to analyze version drift across modules and BOMs to identify the owning authority responsible for the final artifact resolution decision.

Can I fix Spring classpath conflicts without causing regressions in my Kotlin project?

You can fix Spring classpath conflicts without regressions by proposing a minimal, non-invasive adjustment to the dependency graph and running verification steps to ensure build health remains predictable.

How do I diagnose version drift across Gradle BOMs and dependency catalogs?

Diagnosing version drift across Gradle BOMs and catalogs involves identifying conflicting versions across modules and dependency graphs to isolate the root cause of classpath conflicts in Kotlin applications.