Debugging Compose Recompositions
Makes recomposition visible through inspector counts and per-argument change reasons.
Install
git clone https://github.com/skydoves/compose-performance-skills.git ~/.claude/skills-sources/compose-performance-skills && ~/.claude/skills-sources/compose-performance-skills/scripts/install-skills.sh
"Bu composable atlanmalıydı ama atlanmıyor" durumunda ya da bir kararlılık düzeltmesi doğrulanırken
- Author
- Jaewoong Eum (skydoves)
- License
- Apache-2.0
Recomposition leaves no trace in source code, so three instrumentation layers are walked in order: recomposition and skip counts in Layout Inspector, the per-parameter Changed / Unchanged / Uncertain / Static / Unknown classifications added in Hedgehog, and runtime tracing for release builds on a real device. Each status maps to one specific fix, and the closing step is confirming the count actually dropped rather than assuming it did.
Similar skills
scope-guard
SkillCatches an edit that lands outside the project you are in.
Ponytail
SkillArgues for the smallest change that actually solves the problem.
Systematic Debugging
SkillForces reproduce-first debugging instead of speculative patching
Comments(0)
Sign in to comment