hoangnguyen0403/android-agp-upgrade
skills/android/android-agp-upgrade/SKILL.md
Upgrade an Android project to Android Gradle Plugin (AGP) 9. Use when migrating to AGP 9, updating Gradle build files, migrating to built-in Kotlin, or adopting the new AGP DSL.
$ install --global
skillsauthnpx skillsauth add hoangnguyen0403/agent-skills-standard android-agp-upgradeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 8:02 AM46.3s4 files scanned
SKILL.md
- name:
- android-agp-upgrade
- description:
- Upgrade an Android project to Android Gradle Plugin (AGP) 9. Use when migrating to AGP 9, updating Gradle build files, migrating to built-in Kotlin, or adopting the new AGP DSL.
AGP 9 Upgrade Workflow
Priority: P1
Step-by-step workflow for upgrading an Android project to AGP 9.
Prerequisites
- Check current AGP version. If below 8.x, recommend running the AGP Upgrade Assistant in Android Studio first.
- Do NOT use this skill for Kotlin Multiplatform (KMP) projects.
- Verify Gradle, JDK, and Kotlin version compatibility with AGP 9 release notes.
Step 1: Update dependencies
- If KSP (
com.google.devtools.ksp) is used, ensure version 2.3.6+. - If Hilt is used, ensure version 2.59.2+.
- Update AGP to the latest stable 9.x version in the project's build files.
Step 2: Migrate to built-in Kotlin
AGP 9 includes built-in Kotlin support — the org.jetbrains.kotlin.android plugin is no longer needed.
See migration guide for detailed steps.
Step 3: Migrate to the new AGP DSL
AGP 9 introduces a new DSL for android {} blocks. Key changes include namespace handling, build type configuration, and source set declarations.
See DSL migration for before/after examples.
Step 4: Migrate kapt to KSP or legacy-kapt
If the project uses kapt:
- Prefer migrating to KSP where annotation processors support it (Room, Hilt, Moshi).
- For processors without KSP support, use
legacy-kaptas a bridge.
Step 5: Update BuildConfig
If any module uses custom BuildConfig fields, update to the new AGP 9 syntax.
Step 6: Clean up gradle.properties
Remove these flags after migration:
android.builtInKotlinandroid.newDslandroid.uniquePackageNamesandroid.enableAppCompileTimeRClass
Guidelines
- Never write or run Python scripts for build migration.
- Never add
android.disallowKotlinSourceSets=falsetogradle.properties. - Do not run
cleantask when verifying — it wastes time.
Verification
./gradlew helpsucceeds../gradlew build --dry-runsucceeds.- Gradle IDE sync succeeds.
References
- Built-in Kotlin Migration
- DSL Migration Guide
Related Skills
hoangnguyen0403/common-software-requirements
development
VerifiedTrustedCommunity
Standardize SRS and FRS specifications for technical behavior, interfaces, data contracts, quality constraints, and verification mapping. Use when writing SRS, functional specification, system behavior requirements, API/data contracts, or non-functional thresholds.
503SKILL.mdUpdated May 23, 2026
hoangnguyen0403/common-business-requirements
development
VerifiedTrustedCommunity
Standardize BRD and BRD-lite discovery for business goals, stakeholder impact, current-to-future state, and measurable value outcomes. Use when creating BRD, business case, project justification, ROI narrative, or AS-IS to TO-BE scope.
503SKILL.mdUpdated May 23, 2026
hoangnguyen0403/common-tdd
development
VerifiedTrustedCommunity
Implements a strict Red-Green-Refactor loop to ensure zero production code is written without a prior failing test. Use when: creating new features, fixing bugs, or expanding test coverage.
503SKILL.mdUpdated May 10, 2026
hoangnguyen0403/common-product-requirements
testing
VerifiedTrustedCommunity
Standardize PRD discovery and drafting for product scope, user outcomes, requirement IDs, and acceptance criteria. Use when creating PRD, product requirements, feature specification, or acceptance criteria plan.
503SKILL.mdUpdated May 10, 2026