android-update-depslisted

# android-update-deps — controlled dependency review & update A fixed, repeatable procedure to keep an Android (Kotlin/Gradle) project's dependencies current. **Communicate in the language the user is writing in** (default English; mirror Spanish or any other language they use). **Never apply a change without explicit confirmation** — this workflow is gated on purpose (step 5). Bumping dependencies silently is how a working build breaks. > **Commands:** examples use `./gradlew` (Unix/macOS/Git Bash). On **Windows PowerShell** use > `.\gradlew.bat`. If a Bash/shell terminal is available, run them there so `./gradlew` works on any OS. ## Discovery (do this first in a new repo) This skill is generic; every repo differs. Before touching anything, learn the project's shape: 1. **Locate the version catalog** — usually `gradle/libs.versions.toml`. If it doesn't exist, versions may be inline in the `build.gradle.kts` files; say so — those files become the edit target. 2. **Confirm the detection tool.** Check whether `ben-manes/gradle-versions-plugin` is applied (grep for `dependencyUpdates` / `com.github.ben-manes.versions` in the `build.gradle.kts`). If it is **not** applied, offer to add it temporarily. When you do, use its **latest stable version** (look it up on the Gradle Plugin Portal / the plugin's releases) — a dependency-update tool shouldn't introduce an *outdated* dependency; it only needs `0.52.0+` to run on Gradle 9. Configure it so the rest of th