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, and generates committed .stability baseline files via :stabilityDump. - CI integration: Wires :stabilityCheck into GitHub Actions (or other CI) so regressions block merges, with guidance on ignore lists, local opt-outs, and justified baseline updates. - Multiplatform alternative: Points to j-roskopf/ComposeGuard for Compose Multiplatform, desktop, or iOS projects outside the Android Gradle plugin. - Use Case: A team migrating a large app to strong skipping commits a stability baseline, then a PR changing val to var in a shared data class turns the PR check red and names the regressed composable before it ships. ## Quick Start Ask the AI to set up the compose-stability-analyzer plugin in your Gradle modules, generate a stability baseline, and add a stabilityCheck step to your CI workflow.