dependency-manager

Manages Android Gradle dependency versions in libs.versions.toml with compatibility verification.

Updated May 21, 2025
One-click install
npx skills add https://github.com/albertmartorell1975/MeteoMartoCompose --skill dependency-manager-albertmartorell1975
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dependency-manager
Source: https://github.com/albertmartorell1975/MeteoMartoCompose/tree/main/.agents/skills/dependency-manager
Command: npx skills add https://github.com/albertmartorell1975/MeteoMartoCompose --skill dependency-manager-albertmartorell1975

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Updating Android dependencies often leads to build failures caused by incompatible AGP, Kotlin, KSP, or Compose versions, hallucinated version numbers, and redundant or hardcoded declarations scattered across build files. ## Core Features & Use Cases - Compatibility Verification: Checks AGP requirements against official release notes before proposing updates to core libraries like Hilt, KSP, Compose, and Navigation. - TOML Hygiene Enforcement: Enforces kebab-case aliases, BOM usage for Firebase and Compose, KSP instead of KAPT, and bans hardcoded dependency strings in build.gradle.kts files. - Atomic Update Protocol: Applies one change at a time with gradle sync, build, and test verification, plus a strict fail-and-revert rollback policy. - Use Case: When upgrading Hilt in an Android project, the skill verifies the new version's AGP requirement against the project's current AGP, updates only the TOML entry, syncs, builds, and rolls back immediately if anything fails. ## Quick Start Ask the agent to update the Room library version in libs.versions.toml and verify it builds successfully.

Frequently Asked Questions about dependency-manager

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

FAQPage Schema
How do I update Android dependencies in libs.versions.toml safely?▼

Update one dependency at a time in the TOML file, then run a gradle sync and build of the impacted module. If the build fails, revert the TOML file to its last working state instead of guessing alternative versions.

How do I check if a library version is compatible with my AGP version?▼

Identify the current AGP version in libs.versions.toml, then consult the library's official release notes for its minimum AGP requirement. Discard the update if the library requires a higher AGP version than the project uses.

Does the KSP version need to match the Kotlin version?▼

Yes, the KSP version must exactly match the Kotlin version, for example Kotlin 2.0.21 pairs with KSP 2.0.21-1.0.26. Compatibility should never be assumed without verification against official releases.

Should I use KSP or KAPT for Room and Hilt in Android?▼

Use KSP processors instead of KAPT for both Room and Hilt. KSP is the modern annotation processing approach for Kotlin and is the enforced standard in this dependency management protocol.

Why should dependencies not be hardcoded in build.gradle.kts?▼

Hardcoded string literals scatter version information across build files and cause duplication. All dependencies should be declared once in libs.versions.toml and referenced through the libs object, with BOM-managed libraries omitting manual versions.