Does this skill support Gradle version catalogs?

Yes, it specifically targets the gradle/libs.versions.toml file to ensure centralized and standardized dependency management.

Will it automatically add dependencies without my permission?

No, the skill follows a strict approval workflow, requiring explicit user confirmation before any files are modified or new libraries are introduced.

How does the skill find the latest version of a library?

The skill performs an automated web search to identify the most recent stable release of a library before proposing the update.

Does it verify if the new dependency breaks the build?

Yes, after updating the version catalog, the skill runs a sync or build command (like ./gradlew assembleDebug) to ensure project integrity.

Gradle Dependency Manager

Name: Gradle Dependency Manager
Author: AnySoftKeyboard

byAnySoftKeyboard

•

Mobile Development

Automates the process of adding third-party dependencies to Android projects using centralized version catalogs and mandatory approval workflows.

Acerca de

This skill streamlines the integration of new libraries into Android projects by enforcing best practices such as checking for the latest stable versions via web search, updating the gradle/libs.versions.toml file to prevent hardcoded versions, and validating builds after changes. It ensures project stability by requiring explicit user approval and verifying the necessity of each new dependency before implementation, making it an essential tool for maintaining clean and manageable Gradle build systems.

Características Principales

Enforcement of no-hardcoding rules in build scripts
11 GitHub stars
Post-integration build validation using Gradle sync commands
Automated web search for the latest stable library versions
Mandatory user approval workflow to prevent dependency bloat
Centralized management via Gradle Version Catalogs (TOML)

Casos de Uso

Migrating inline dependency declarations to a centralized version catalog
Adding a new networking library like Retrofit to an Android project safely
Updating existing project dependencies to their latest stable releases

Acerca de

Características Principales

Enforcement of no-hardcoding rules in build scripts
11 GitHub stars
Post-integration build validation using Gradle sync commands
Automated web search for the latest stable library versions
Mandatory user approval workflow to prevent dependency bloat
Centralized management via Gradle Version Catalogs (TOML)

Casos de Uso

Migrating inline dependency declarations to a centralized version catalog
Adding a new networking library like Retrofit to an Android project safely
Updating existing project dependencies to their latest stable releases