kotlin-idiomatic-refactorer-spring-aware

Refactor Kotlin code toward clearer, more idiomatic design without breaking Spring behavior, serialization, persistence, or public contracts. Use when Java-flavored Kotlin needs cleanup, domain modeling should become more expressive, or boilerplate should be reduced, but the refactoring must remain safe for proxies, Jackson, JPA, configuration binding, and existing tests.

1.14x

Quality

92%

Does it follow best practices?

Impact

88%

1.14x

Average score across 2 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, token-efficient instruction-only skill with a clear sequenced workflow and explicit validation checkpoints. Its main gap is actionability: it names the right Kotlin constructs and rules but includes no concrete before/after code examples to make the refactorings directly executable.

Suggestions

Add 1-2 short before/after Kotlin snippets (e.g., imperative if-chain → exhaustive `when`, or Java-style constructor → idiomatic constructor injection) to lift actionability from guidance to copy-paste-ready.

Include an explicit verification/revert feedback loop in 'Refactor In This Order' (e.g., 'if tests fail after a step, revert that step before proceeding') to make error recovery concrete.

Optionally move 'Advanced Refactoring Traps' and 'Kotlin Language Nuances' into a linked reference file so the top-level overview stays scannable.

Dimension	Reasoning	Score
Conciseness	Lean bullet-driven guidance that assumes Claude's competence — it never explains what Kotlin, Spring, Jackson, or JPA are, and each line is a genuine heuristic or rule with no padding.	3 / 3
Actionability	Names specific constructs (`when`, `sealed class`, `data class`, value classes, extension functions) with clear rules, but provides no code or before/after examples, so the guidance is concrete yet not copy-paste ready or fully executable.	2 / 3
Workflow Clarity	'Refactor In This Order' gives a clear 5-step sequence with explicit validation checkpoints — 'Characterize current behavior with tests' and 'Re-check proxy, serialization, and persistence compatibility' — plus an incremental-change safety mechanism.	3 / 3
Progressive Disclosure	A single well-organized SKILL.md with clearly labeled sections (Mission, Read First, Refactor In This Order, traps, safety rules, Output Contract, Guardrails); no nested references and no need for external bundle files, so navigation is straightforward.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A high-quality description: third-person, concrete, with an explicit 'Use when' trigger and natural terminology that clearly scopes a distinct Spring-aware Kotlin refactoring niche. No fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists concrete refactoring targets and the specific framework boundaries it preserves — 'Spring behavior, serialization, persistence, or public contracts' plus 'proxies, Jackson, JPA, configuration binding, and existing tests' — rather than vague language.	3 / 3
Completeness	Explicitly answers both what ('Refactor Kotlin code toward clearer, more idiomatic design...') and when via a present 'Use when Java-flavored Kotlin needs cleanup, domain modeling should become more expressive, or boilerplate should be reduced' clause.	3 / 3
Trigger Term Quality	Uses natural developer terms a user would actually say — 'refactor', 'Kotlin', 'Java-flavored Kotlin', 'cleanup', 'boilerplate', 'Spring', 'Jackson', 'JPA' — with good coverage of common phrasings.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche — Spring-aware Kotlin idiomatic refactoring — with triggers unlikely to fire for unrelated skills; the framework-safety framing distinguishes it from generic Kotlin or Spring skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: JetBrains/skills
Path: kotlin-idiomatic-refactorer-spring-aware/SKILL.md
Commit: e0f258b

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.