agp-9-upgrade

Étoiles8

Forks1

Mis à jour24 mai 2026 à 14:10

Use this when: upgrade AGP, migrate Android Gradle Plugin, AGP version upgrade, AGP 9 migration, update build.gradle AGP version, Android build plugin upgrade, gradle plugin compatibility. Upgrades, or migrates, an Android project to use Android Gradle Plugin (AGP) version 9. Do not use this skill for migrating Kotlin Multiplatform (KMP) projects.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

drewid74

drewid74/ai_skills

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	agp-9-upgrade
description	Use this when: upgrade AGP, migrate Android Gradle Plugin, AGP version upgrade, AGP 9 migration, update build.gradle AGP version, Android build plugin upgrade, gradle plugin compatibility. Upgrades, or migrates, an Android project to use Android Gradle Plugin (AGP) version 9. Do not use this skill for migrating Kotlin Multiplatform (KMP) projects.
license	Complete terms in LICENSE.txt
metadata	{"author":"Google LLC","last-updated":"2026-04-17","keywords":["Android Gradle Plugin 9","AGP 9","AGP Upgrade","AGP Migration","New AGP DSL","Migrate to built-in Kotlin"]}

Migration guide

See the AGP 9 migration guide for the major changes, many breaking, in AGP 9 compared to AGP 8.

Requirements

If the user requests to update or migrate to AGP 9, first check the AGP version used in the project. If it is lower than 9, stop and ask the user to run the AGP Upgrade Assistant in Android Studio to update to the latest stable version of AGP, and confirm when done. The user may also request that this requirement be skipped; if this is the case, you should update the version of AGP to the latest stable version as part of the AGP 9 migration. See the AGP 9 migration guide for how to do this.

Each version of AGP has its own set of compatibilities with other tools, such as Gradle, JDK, and Kotlin. The release notes for each of these versions will include a Compatibility table indicating the minimum versions for these tools.

Do not use this skill for KMP projects, as they are unsupported.

Steps

If AGP is already at 9 or higher, then do the following:

Step 1: Update dependencies

If KSP (com.google.devtools.ksp) is used in the project, ensure it is on version 2.3.6 or higher.

If Hilt is used in the project, ensure it is on version 2.59.2 or higher.

Step 2: Migrate to built-in Kotlin

See the guide for detailed information.

Step 3. Migrate to the new AGP DSL

See the guide for detailed information.

See also gradle-recipes for examples on how to migrate old code to code that is compatible with AGP 9 and the new DSL.

Step 4. Migrate kapt to KSP or legacy-kapt

If KSP (com.google.devtools.ksp) or kapt (org.jetbrains.kotlin.kapt) are used in the project, see KSP, kapt, and legacy-kapt for detailed migration steps.

Step 5. BuildConfig

If any Android module contains custom BuildConfig fields, see BuildConfig for detailed information.

Step 6. Update gradle.properties

After the migration, check gradle.properties. Remove the following flags:

android.builtInKotlin
android.newDsl
android.uniquePackageNames
android.enableAppCompileTimeRClass

Additionally, delete all temporary files you've created.

Guidelines

Never write or run python scripts.
Only search the Gradle dependency cache when inspecting external dependencies, and only as a last resort.
Never add android.disallowKotlinSourceSets=false to gradle.properties.
When verifying changes, don't run the clean task. This is a waste of time.

Verification

After migration, verify the following:

Gradle IDE sync succeeds.
./gradlew help succeeds.
./gradlew build --dry-run succeeds.

Troubleshooting

Paparazzi v2.0.0-alpha04 and lower versions have issues with AGP 9. See references/paparazzi-gradle-9.md for details.

Automated / AI-Assisted Testing Tooling (local baseline)

Use the currently available local toolchain for automation-first Android validation:

Primary tools available: adb, emulator, repo ./gradlew / ./gradlew.bat, java, python3, node, npm, bun, aapt, aapt2, gh
Commonly referenced but currently unavailable in PATH: android CLI binary, sdkmanager, avdmanager, maestro, apkanalyzer, bundletool

Recommended unattended validation loop:

Run deterministic gates each iteration:
- :core:test, :app:test, :app:assembleDebug, :app:lint
If a device is present (adb devices), run connected instrumentation:
- :app:connectedDebugAndroidTest
Persist per-iteration logs and summaries under .sisyphus/evidence/.
Bucket failures by signature (for flaky analysis), especially:
- ComposeTimeoutException
- No compose hierarchies found
- device transport errors (No connected devices, device ... not found)

For managed devices where keep-awake cannot be enabled, use a sleep-tolerant loop:

continue non-device gates every cycle
classify connected runs as PASS / FAIL / SKIP(no-device)
avoid treating temporary device sleep as total run failure.

Plus depuis ce dépôt

même dépôt

continue-from-accepted

drewid74/ai_skills

Continue iterative work from the last ACCEPTED result plus only the new requested change, instead of replaying the conversation. Use during long multi-turn editing of a document, config, or code file; when the user says "keep going from what we had", asks for a follow-up change to something already approved, or is near plan/token limits in an iterative session. Saves one integrity-checked accepted result, builds a minimal continuation prompt, and never carries rejected drafts or transcript history forward.

2026-07-308

quality-test-engineer

drewid74/ai_skills

Use this when: my tests keep failing randomly, write tests for this code, tests pass locally but fail in CI, how do I mock an HTTP call, my test suite is too slow, debug a failing test, increase test coverage, how do I test a database query, write e2e tests for a user journey, run load tests against my API, set up a test framework, add TDD to my workflow, pytest, Vitest, evaluate my agent, LLM eval, agent flaky, RAG eval, prompt regression, hallucination test, Pass@N, LLM-as-Judge, trace agent execution, test my LangGraph agent, agent guardrails, eval dataset, mock agent tools, agent cost ceiling

2026-06-118

api-integration

drewid74/ai_skills

Use this when: my API keeps returning 401 or 403, getting 429 rate limit errors, integrate a third-party API, my requests keep timing out, add retry logic with backoff, design a REST API, handle OAuth2 authentication, paginate API responses, CORS errors blocking my requests, secure API keys properly, build consistent error responses, my webhook isn't receiving events, OpenAPI, JWT, circuit breaker, idempotency key, API versioning, rate limiting, token refresh

2026-06-068

cicd-pipeline

drewid74/ai_skills

Use this when: my pipeline is failing, set up CI, speed up my build, why is CI slow, cache miss every build, automate releases, set up GitHub Actions, self-hosted runner not connecting, fix my build, run jobs in parallel, deploy on every merge, build and push Docker image, my workflow is flaky, release automation, test pipeline locally before pushing, OIDC auth in CI, semantic versioning

2026-06-068

code-reviewer

drewid74/ai_skills

Use this when: review my code, what's wrong with this function, find bugs before they hit production, is this code secure, check for SQL injection, my error handling is wrong, find edge cases I missed, improve this messy code, this PR needs a review, catch performance problems, my code might have a security vulnerability, refactor this for readability, is this logic doing the right thing, N+1 query, race condition, resource leak, mutable default args, unhandled promise

2026-06-068

data-engineering

drewid74/ai_skills

Use this when: build a data pipeline, my pipeline is not idempotent, clean messy data, convert CSV to Parquet, my data has duplicates, validate schema at ingestion, pipeline fails on re-run, process files larger than memory, schedule a recurring job, upstream schema changed and broke my pipeline, migrate data between systems, query Parquet without loading it, deduplicate records, batch vs stream processing, DuckDB for analytics, choose an orchestrator, slow pandas pipeline

2026-06-068

name	agp-9-upgrade
description	Use this when: upgrade AGP, migrate Android Gradle Plugin, AGP version upgrade, AGP 9 migration, update build.gradle AGP version, Android build plugin upgrade, gradle plugin compatibility. Upgrades, or migrates, an Android project to use Android Gradle Plugin (AGP) version 9. Do not use this skill for migrating Kotlin Multiplatform (KMP) projects.
license	Complete terms in LICENSE.txt
metadata	{"author":"Google LLC","last-updated":"2026-04-17","keywords":["Android Gradle Plugin 9","AGP 9","AGP Upgrade","AGP Migration","New AGP DSL","Migrate to built-in Kotlin"]}

Migration guide

See the AGP 9 migration guide for the major changes, many breaking, in AGP 9 compared to AGP 8.

Requirements

Do not use this skill for KMP projects, as they are unsupported.

Steps

If AGP is already at 9 or higher, then do the following:

Step 1: Update dependencies

If KSP (com.google.devtools.ksp) is used in the project, ensure it is on version 2.3.6 or higher.

If Hilt is used in the project, ensure it is on version 2.59.2 or higher.

Step 2: Migrate to built-in Kotlin

See the guide for detailed information.

Step 3. Migrate to the new AGP DSL

See the guide for detailed information.

See also gradle-recipes for examples on how to migrate old code to code that is compatible with AGP 9 and the new DSL.

Step 4. Migrate kapt to KSP or legacy-kapt

If KSP (com.google.devtools.ksp) or kapt (org.jetbrains.kotlin.kapt) are used in the project, see KSP, kapt, and legacy-kapt for detailed migration steps.

Step 5. BuildConfig

If any Android module contains custom BuildConfig fields, see BuildConfig for detailed information.

Step 6. Update gradle.properties

After the migration, check gradle.properties. Remove the following flags:

android.builtInKotlin
android.newDsl
android.uniquePackageNames
android.enableAppCompileTimeRClass

Additionally, delete all temporary files you've created.

Guidelines

Never write or run python scripts.
Only search the Gradle dependency cache when inspecting external dependencies, and only as a last resort.
Never add android.disallowKotlinSourceSets=false to gradle.properties.
When verifying changes, don't run the clean task. This is a waste of time.

Verification

After migration, verify the following:

Gradle IDE sync succeeds.
./gradlew help succeeds.
./gradlew build --dry-run succeeds.

Troubleshooting

Paparazzi v2.0.0-alpha04 and lower versions have issues with AGP 9. See references/paparazzi-gradle-9.md for details.

Automated / AI-Assisted Testing Tooling (local baseline)

Use the currently available local toolchain for automation-first Android validation:

Primary tools available: adb, emulator, repo ./gradlew / ./gradlew.bat, java, python3, node, npm, bun, aapt, aapt2, gh
Commonly referenced but currently unavailable in PATH: android CLI binary, sdkmanager, avdmanager, maestro, apkanalyzer, bundletool

Recommended unattended validation loop:

Run deterministic gates each iteration:
- :core:test, :app:test, :app:assembleDebug, :app:lint
If a device is present (adb devices), run connected instrumentation:
- :app:connectedDebugAndroidTest
Persist per-iteration logs and summaries under .sisyphus/evidence/.
Bucket failures by signature (for flaky analysis), especially:
- ComposeTimeoutException
- No compose hierarchies found
- device transport errors (No connected devices, device ... not found)

For managed devices where keep-awake cannot be enabled, use a sleep-tolerant loop:

continue non-device gates every cycle
classify connected runs as PASS / FAIL / SKIP(no-device)
avoid treating temporary device sleep as total run failure.