What problem does it solve? Jetpack Compose stability issues — a composable becoming unskippable or a parameter flipping from stable to unstable — are invisible until recomposition regressions hit production. This Skill turns stability into a build gate: snapshot every composable's stability into a committed .stability baseline and fail CI when a change makes anything less stable. ## Core Features & Use Cases - Baseline generation: Run stabilityDump to write a human-readable .stability file per module and commit it as the team's shared contract. - CI regression gating: Run stabilityCheck after compilation to compare current output against the baseline, failing the build on ~ regressions while optionally ignoring non-regressive changes. - Deliberate baseline updates: Accept intentional stability changes through reviewed stabilityDump commits with justification, and exclude @Preview or scaffolding composables via @IgnoreStabilityReport and ignored* lists. - Use Case: A PR adds a List<Pokemon> parameter to a hot composable; the CI stability job (with needs: build) fails, naming the composable and its stability change, before the regression ships. ## Quick Start Set up the Compose Stability Analyzer plugin in my Gradle module, generate and commit the stability baseline, and wire a stabilityCheck job into my GitHub Actions CI that fails on regressions.
