codefmt

Reformat source code in this project using its own code-style settings — through the IntelliJ IDE when it's running, otherwise via the project's own formatter (Spotless / google-java-format / palantir-java-format) as a fallback. Use this whenever the user asks to format, reformat, tidy, "prettify", fix indentation, or optimize imports on Java/Kotlin/XML/etc. files — whether it's a single named file, a selected block or line range, a group of named files, or all uncommitted (git-changed) files. This skill is also normally invoked after any editing of files — apply it to the files you just created or changed once the edits are done, so the result stays consistent with the project's code style.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%Weight 40%Scale 1-5

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

The body is a well-structured orchestration layer: concise, with executable routing and verification commands, a clear two-path workflow with explicit validation, and clean one-level-deep references to real bundle files. The only minor gap is that the literal formatting commands live in the referenced files rather than the body itself.

Suggestions

Consider including one inline example format command per path (e.g. a representative Spotless/google-java-format invocation) so the body is executable without opening a reference for the common single-file case.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no padding or explanation of concepts Claude already knows; every sentence (the two-path framing, the probe-first directive, the no-diff caveat) earns its place and assumes Claude's competence.	5 / 5
Actionability	Provides concrete, executable commands for routing and verification (`steroid_list_projects`, `ToolSearch(...)`, `git diff --stat <paths>`) with clear decision logic; the core format execution itself is delegated to the referenced files, leaving a minor gap in the body.	4 / 5
Workflow Clarity	Clear sequence (probe -> pick path -> format -> verify via git diff) with an explicit validation checkpoint ('A reformat that produces no diff is a valid outcome') and feedback for the IDE-unreachable block case, satisfying the batch-operation validation requirement.	5 / 5
Progressive Disclosure	Clear overview with well-signaled one-level-deep references to references/ide.md and references/fallback.md (both verified present), with orchestration in the body and detail/scripts split into the bundle for easy navigation.	5 / 5
	Total	19 / 20 Passed

Description

100%Weight 40%Scale 1-5

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

The description is excellent: it states concrete capabilities, lists natural trigger terms with synonyms, explicitly covers both what and when, and carves out a distinct niche. It uses third-person voice for the capability statement with a standard 'Use this' trigger clause.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions (reformat via IntelliJ IDE, fallback through Spotless/google-java-format/palantir-java-format, optimize imports) and concrete targets (single file, block/line range, group of files, uncommitted git-changed files), giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both what ('Reformat source code in this project using its own code-style settings') and when ('Use this whenever the user asks to format, reformat, tidy...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural trigger terms including synonyms ('format, reformat, tidy, "prettify", fix indentation, optimize imports') plus file-type coverage (Java/Kotlin/XML), matching phrases users would actually say.	5 / 5
Distinctiveness Conflict Risk	Clear niche (project code-style formatting via IntelliJ IDE with external-formatter fallback) with distinct, specific triggers and minimal overlap risk with other skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Amplicode/spring-skills
Path: skills/codefmt/SKILL.md
Commit: bf19b3c

Reviewed: 5 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.