agp-9-upgrade

Upgrade Android projects to AGP 9 with compatibility checks and migration steps.

1|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/premex-ab/claude-marketplace --skill agp-9-upgrade-premex-ab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agp-9-upgrade
Source: https://github.com/premex-ab/claude-marketplace/tree/main/plugins/android-agp-9-upgrade/skills/agp-9-upgrade
Command: npx skills add https://github.com/premex-ab/claude-marketplace --skill agp-9-upgrade-premex-ab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Updating an Android project to Android Gradle Plugin (AGP) 9 can break builds and developer workflows due to major breaking changes and required migrations.

Core Features & Use Cases

  • Pre-migration checks and gating: Validates the current AGP version and directs users to the AGP Upgrade Assistant when the project is below AGP 9.
  • Dependency compatibility updates: Ensures KSP and Hilt versions meet AGP 9 requirements before deeper migration steps.
  • Step-by-step project migration: Guides migration to built-in Kotlin, transitions to the new AGP DSL, migrates kapt to KSP or legacy-kapt, updates BuildConfig usage, and cleans up obsolete gradle.properties flags.
  • Practical verification: Specifies what to verify after migration (IDE sync, gradlew help, and gradlew build with dry-run).
  • Troubleshooting support: Includes targeted guidance for Paparazzi compatibility issues with Gradle 9 / AGP 9.

Example: If your repo currently builds on AGP 8 using kapt and custom BuildConfig fields, this skill helps you upgrade to AGP 9, move kapt usage toward KSP (or legacy-kapt when needed), and verify the migration with safe, non-clean checks.

Quick Start

Tell the AI to migrate your Android project to AGP 9 and follow the required steps and verification checklist for dependencies, DSL, Kotlin migration, kapt/KSP, BuildConfig, and gradle.properties cleanup.

Frequently Asked Questions about agp-9-upgrade

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

FAQPage Schema
How do I migrate my Android project to AGP 9?

Migrating to AGP 9 requires validating your current AGP version, updating KSP and Hilt dependencies, adopting the new AGP DSL, migrating kapt to KSP, and verifying the build with gradlew commands. This prevents common migration breakages.

How do I handle kapt when upgrading to AGP 9?

When upgrading to AGP 9, migrate kapt usage to KSP or transition to legacy-kapt where necessary. This handles annotation processing transitions while maintaining compatibility with the new Android Gradle Plugin version.

Does AGP 9 migration support Kotlin Multiplatform projects?

AGP 9 migration does not support Kotlin Multiplatform (KMP) projects. The process targets standard Android projects using KSP, Hilt, kapt, custom BuildConfig fields, or Paparazzi.

What should I verify after migrating to Android Gradle Plugin 9?

After migrating to Android Gradle Plugin 9, verify IDE sync, run gradlew help, and execute gradlew build with a dry-run. These non-clean checks confirm the migration succeeded without introducing build errors.

Why does Paparazzi fail after upgrading to Gradle 9 and AGP 9?

Paparazzi compatibility issues with Gradle 9 and AGP 9 cause build failures after upgrading. The migration process includes targeted troubleshooting guidance to resolve these specific Paparazzi compatibility conflicts.

Do I need to update BuildConfig fields for AGP 9?

Yes, updating custom BuildConfig field usage is required during AGP 9 migration. The process guides you through updating BuildConfig declarations to align with the new Android Gradle Plugin standards.