← ClaudeAtlas

cmp-verifylisted

Use when deciding when to build, when fixing a Gradle, KSP, Koin or Compose resources failure that cmp-gates reported as open, or when reading gate output in this Compose Multiplatform project — the build schedule, how to read the output, and the recipes for common Kotlin Multiplatform failures, including NoDefinitionFoundException at runtime. The gates themselves are run with cmp-gates.
whinstudio/skills · ★ 0 · AI & Automation · score 63
Install: claude install-skill whinstudio/skills
# Verify and fix builds ## 1. The gates Run the gates listed in `CLAUDE.md` under *Definition of done*, in that order. - Run them with `cmp-gates`: it runs them in a separate subagent and returns a short report, so the Gradle log stays out of this session. Run a gate directly only to reproduce one failure `cmp-gates` reported as open. - The list names the exact commands: the Android debug build, the iOS simulator compile, detekt (only when the project has it) and the test run. Run each one as written, as its own command. `CLAUDE.md` is the source of truth; do not substitute other task names. - `./gradlew build` is not used: it also links release iOS frameworks and runs out of memory. - A red detekt gate is fixed with `cmp-detekt`; a red or empty test gate with `cmp-testing`. ## 2. When to build - Run the Android gate after each screen or module is in place, not after every change. Wrong imports are the most common failure; one run finds all of them. - Run the iOS gate twice: once midway, after the first module and any `expect`/`actual` code or `commonMain` code that touches time, files, formatting or other platform APIs, and once in the final pass. Android compiling says nothing about iOS. - detekt and tests come once the code stands; the final pass runs every gate, in order. ## 3. Read the output correctly - A success claim rests on what ran: the task lines in the log and, for tests, the test count. The exit code alone is not evidence. - The test gate