What problem does it solve? Jetpack Compose stability silently regresses when a new var or unstable parameter slips into a shared data class, disabling skipping across many screens with no build warning. This Skill sets up a CI gate that diffs a committed stability baseline on every pull request and fails the build when stability regresses. ## Core Features & Use Cases - Baseline generation and validation: Applies the skydoves/compose-stability-analyzer Gradle plugin, configures the composeStabilityAnalyzer { stabilityValidation { ... } } DSL, generates .stability baseline files with :stabilityDump, and enforces them with :stabilityCheck. - CI integration: Wires stabilityCheck into a GitHub Actions job alongside assemble, uploads stability diff reports on failure, and defines rules for justified baseline updates and conservative ignore lists. - Multiplatform alternative: Points to j-roskopf/ComposeGuard for Compose Multiplatform (KMP, desktop, iOS) projects outside the Android Gradle plugin. - Use Case: A team migrating a large app to strong skipping adds the plugin to every UI module, commits the .stability baseline, and any PR that turns a val into a var in a shared data class turns the PR check red with the regressed composable named. ## Quick Start Ask the AI to set up the compose-stability-analyzer plugin in your Gradle modules, generate and commit the stability baseline, and add a stabilityCheck step to your CI workflow.
