dependency-execution

Applies dependency updates, resolves version conflicts, and updates build configurations from design mappings.

1|1|Updated May 16, 2026
One-click install
npx skills add https://github.com/vanduc2514/hackathon-lablab-ibm-bob --skill dependency-execution-vanduc2514
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dependency-execution
Source: https://github.com/vanduc2514/hackathon-lablab-ibm-bob/tree/main/.bob/skills/dependency-execution
Command: npx skills add https://github.com/vanduc2514/hackathon-lablab-ibm-bob --skill dependency-execution-vanduc2514

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Migrating a project to new framework versions requires updating dependency manifests, resolving version conflicts, and upgrading build tools, which is error-prone when done manually across pom.xml, package.json, or build.gradle files. ## Core Features & Use Cases - Dependency Manifest Updates: Applies dependency substitutions from a design-phase mapping to Maven, Gradle, and npm manifests. - Conflict Resolution: Resolves version conflicts using dependency management, exclusions, and BOM imports. - Build Verification: Runs clean builds, test suites, security scans, and license checks to confirm stability. - Use Case: When migrating from Spring Boot 2.7 to 3.2, use this Skill to replace javax.validation with jakarta.validation, upgrade the compiler plugin to Java 21, and verify all 172 tests still pass. ## Quick Start Apply the dependency updates from design_dependency_mapping.md to my pom.xml and verify the build passes.

Frequently Asked Questions about dependency-execution

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

FAQPage Schema
How do I update dependencies when migrating Spring Boot 2.7 to 3.2?▼

Update the spring-boot-starter-parent version to 3.2.0, replace javax.validation with jakarta.validation-api, and set the compiler plugin to Java 21. Then run a clean build and full test suite to verify compatibility.

How to resolve Maven dependency version conflicts?▼

Use dependencyManagement to enforce a single converged version across transitive dependencies, or add exclusions to remove conflicting transitive artifacts. Importing a BOM like spring-cloud-dependencies also keeps related versions consistent.

Does this work with Gradle and npm as well as Maven?▼

Yes, the process covers pom.xml, build.gradle, and package.json manifests. For Gradle it updates plugin versions and java sourceCompatibility, and the same conflict resolution and verification steps apply.

Why does my build fail after a dependency update?▼

Builds commonly fail from unresolved transitive conflicts, API changes between major versions, or outdated build plugins. Review the dependency tree for unexpected versions, update build tool plugins, and check the execution report's conflict resolutions.

How do I roll back dependency changes if tests fail?▼

Commit or tag the current dependency state before applying updates so you can revert with git checkout of the previous manifest. Then run a clean build to restore the prior working state.