skills.rest
yalishevant
yalishevantCOMMUNITY
Explore all skills by this author →
GitHub

dependency-conflict-resolver

Diagnose Gradle and Spring dependency conflicts in Kotlin multi-module builds.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose and resolve Gradle and Spring dependency conflicts, version drift, and binary incompatibilities in Kotlin applications.

Core Features & Use Cases

  • Dependency graph analysis and conflict identification across multi-module builds
  • BOM-aware resolution guidance and minimal, safe fixes
  • Clear root-cause explanations and recommended ownership alignment for dependency authorities

Quick Start

Run ./gradlew dependencies and inspect the graph to begin diagnosing conflicts.

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 Gradle dependency conflicts in a Kotlin project?▼

Resolve Gradle dependency conflicts by running ./gradlew dependencies to inspect the graph, identifying the winning version, and applying a minimal safe fix to align dependency authorities across modules.

How do I fix Spring BOM version conflicts with explicit versions in Gradle?▼

Fix Spring BOM version conflicts by identifying which dependency authority should own the version, then removing or aligning the explicit version overrides that cause binary incompatibilities in your build.

Why does my multi-module Gradle build have binary incompatibilities and version drift?▼

Binary incompatibilities and version drift occur when different modules pull in conflicting transitive dependency versions, requiring graph analysis to identify the winning version and the correct authority to enforce it.

What's the best way to diagnose Spring dependency version conflicts across modules?▼

Diagnose Spring dependency version conflicts by analyzing the Gradle dependency graph to find the winning version, determining the correct ownership authority, and applying a minimal safe fix with verifiable steps.

Can I use this Gradle dependency conflict resolution approach for Kotlin multi-module builds?▼

Yes, this approach specifically applies to Kotlin multi-module builds experiencing version drift, binary incompatibilities, and BOM-versus-explicit-version issues, providing minimal safe fixes with verifiable steps.

How do I know which dependency authority should own the winning version in Gradle?▼

Identify the winning version by inspecting the Gradle dependency graph, then determine the correct authority—such as a BOM or explicit declaration—based on which ownership alignment provides the safest minimal fix.

Related Skills

Explore More Software Engineering Skills→
mattbobambrosemattbobambrose
1

add-dependency

Resolve Maven coordinates and inject dependencies into Gradle version catalogs.

Community
Advanced
baldimirbaldimir

maven-dependency-update

Align Maven pom.xml dependencies with the Quarkus BOM.

Community
Advanced
iceflowericeflower
1

gradle-convention

Standardizes Gradle builds for Kotlin and Spring Boot multi-module projects with caching and parallel execution.

Community
Intermediate
JetBrainsJetBrains
302

dependency-conflict-resolver

Diagnose Gradle and Spring classpath conflicts in Kotlin applications.

Official
Advanced