Codex Review Kotlin JVM and KLIB ABI Baselines
Check that intended Executables public API changes match JVM and KLIB baselines and reach the relevant Gradle validation task.
中文Install in Codex
Use an Executables checkout, the project Gradle Wrapper, and a suitable Kotlin toolchain. The exercise uses Windows PowerShell.
- Copy the pinned `.codex/skills/executables-abi-maintenance/` directory into `.agents/skills/executables-abi-maintenance/` in the project.
- Read `AGENTS.md`, `files/build.gradle.kts`, and both ABI baseline files under `files/api/` in Codex.
Example task
Add a public function in a local demo branch and run `.\gradlew.bat :executables-files:check --dry-run`. Compare the expected signature differences in JVM and KLIB baselines.What to check
The report identifies the task path, expected baseline changes, and any validation that still needs the Linux CI environment.
Original SKILL.md on GitHub · Updated
Frequently asked question
Does a JVM baseline change cover the whole check?
Inspect JVM and KLIB output separately and verify the task conditions used by CI.