Skill

Debugging Compose Recompositions

Makes recomposition visible through inspector counts and per-argument change reasons.

GitHub stars

488

Repository on GitHub

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

Triggers on

"Bu composable atlanmalıydı ama atlanmıyor" durumunda ya da bir kararlılık düzeltmesi doğrulanırken

Needs tools

ReadBash

Author: Jaewoong Eum (skydoves)
License: Apache-2.0

Repositoryhttps://github.com/skydoves/compose-performance-skills

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.

Comments(0)

No comments yet — be the first.

Similar skills

Debugging Strategies

Skill

Replaces guess-and-check debugging with a narrowing procedure.

Tests & Debugging

Diagnosing Compose Stability

Skill

Reads the Compose compiler reports to name which parameters are unstable and why.

Coding Workflows

Error Debugging

Skill

Works backward from a symptom to the release that caused it, then writes the query catching a repeat.

Tests & Debugging