Menu
Makes a minimal reproduction of a Frontend-related bug as a diagnostic test
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/JetBrains/kotlin --skill minimize-repro-for-diagnostic-testThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
| name | minimize-repro-for-diagnostic-test |
| description | Makes a minimal reproduction of a Frontend-related bug as a diagnostic test |
| user-invocable | true |
| disable-model-invocation | true |
Ask a user for some details, whether it's some YouTrack issue or some locally built user project. For a local user project, ask for details like where an error had happened, what is the context around, if it's opened in the IDE.
Ask a user whether they need a separate test data file with an initial test version.
If a case depends on some dependencies, be it other sources or some libraries, if needed, use their API description on the web.
For a local user project if it's open in the IDE, use JetBrains MCP resolution to determine the context, e.g., by getting symbols info.
Using information from tests description, make a first version of the test which contains some wide context needed to reproduce the issue, like all necessary/referenced declarations dumped (including Java files and dependencies in separate file).
Make sure that the problem is reproduced by running a test, and if it's not, add some more context, if you fail for a couple of times, then stop.
Try to remove or trivialize different parts of the context used for the repro. If it stops failing for one of them, try doing something under another angle, like trivializing a different part.
If it's an inference-related issue, dump the inference logs.
Bumps the Gradle wrapper/distribution version that BUILDS the Kotlin project itself — the version behind `./gradlew`, defined by `gradle/wrapper/gradle-wrapper.properties`. Covers the wrapper regeneration and the version-specific fallout that follows it: removed/deprecated Gradle DSL, dependency-verification metadata, the Gradle Module Metadata fixtures, and the KGP functional tests. This is DISTINCT from the two sibling skills — it is NOT `build-tools-bump-gradle-api` (which bumps GRADLE_COMMON_COMPILE_API_VERSION, the API that plugins compile against) and NOT `build-tools-bump-gradle-in-tests` (which extends the KGP integration-test version matrix). Manual invocation only: a full run downloads a distribution, rewrites `gradle/verification-metadata.xml`, and drives `publish`, `testClasses` and `functionalTest` — hours of wall clock and a heavily mutated checkout — so it starts only when the user explicitly asks for `/build-bump-gradle-version`.
Bump the maximum supported Gradle version in the `kotlin-gradle-plugin-integration-tests` project. Use this whenever the user asks to bump Gradle in integration tests, add a new Gradle X.Y.Z to the test matrix, update `MAX_SUPPORTED` Gradle, "run tests against the new Gradle release", or anything else that sounds like extending the integration test matrix to a newer Gradle. The procedure spans four touch points across three files that must stay in lock-step (`TestVersions.kt`, `build.gradle.kts`, `GradleCompatibilityIT.kt`); reach for this skill even when the user mentions only one of those files, because editing by hand routinely desyncs them.
Add KaResolver resolveSymbol/resolveCall support for a PSI type
Based on SOC occupation classification
