How do I install the Codefmt skill?

Run npx skillmds@latest add amplicode/codefmt in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Codefmt safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Codefmt?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Codefmt free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Codefmt?

amplicode (@amplicode) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Codefmt by amplicode — Agent Skill

Name: Codefmt
Author: amplicode

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.

amplicode 7b54af1 7 files · 22.4 KB Updated Sep 17, 2026

File contents

Format source files with the project's code style

Two paths reach the same code style: the IDE applies it through IntelliJ's own formatter (highest fidelity, keeps the IDE's VFS/PSI caches consistent); the CLI fallback applies it through the project's own external formatter (Spotless / google-java-format / palantir-java-format) when the IDE isn't reachable.

Pick the path

Probe FIRST, here, before loading either reference — so you read only the one you need. Call steroid_list_projects (via ToolSearch("steroid list projects execute code") if the tool schema isn't loaded):

It returns the repo you're in → IDE path: note that entry's project_name (the opaque routing key, not the human-readable name) and follow references/ide.md. Its recipes start already knowing the project_name — don't re-probe.
It fails, or the repo isn't listed → CLI fallback path: follow references/fallback.md (detects Spotless / java-format and runs it in the console) and tell the user up front you're using the external-formatter fallback because the IDE wasn't reachable.

Block / line-range formatting (IDE recipe 2) is IDE-only — there's no faithful CLI equivalent. If the user asked for a block and the IDE is unreachable, say so rather than silently reformatting the whole file.

Both paths end the same way: run git diff --stat <paths> and report what actually changed. A reformat that produces no diff is a valid outcome — the files already conform to the style; say so plainly rather than implying work was done.

---name: codefmtdescription: 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.---# Format source files with the project's code styleTwo paths reach the same code style: the **IDE** applies it through IntelliJ's ownformatter (highest fidelity, keeps the IDE's VFS/PSI caches consistent); the**CLI fallback** applies it through the project's own external formatter (Spotless/ google-java-format / palantir-java-format) when the IDE isn't reachable.## Pick the pathProbe FIRST, here, before loading either reference — so you read only the one youneed. Call `steroid_list_projects` (via `ToolSearch("steroid list projectsexecute code")` if the tool schema isn't loaded):- It returns the repo you're in → **IDE path**: note that entry's `project_name` (the opaque routing key, **not** the human-readable `name`) and follow [`references/ide.md`](references/ide.md). Its recipes start already knowing the `project_name` — don't re-probe.- It fails, or the repo isn't listed → **CLI fallback path**: follow [`references/fallback.md`](references/fallback.md) (detects Spotless / java-format and runs it in the console) and tell the user up front you're using the external-formatter fallback because the IDE wasn't reachable.Block / line-range formatting (IDE recipe 2) is **IDE-only** — there's no faithfulCLI equivalent. If the user asked for a block and the IDE is unreachable, say sorather than silently reformatting the whole file.Both paths end the same way: run `git diff --stat <paths>` and report whatactually changed. A reformat that produces **no diff** is a valid outcome — thefiles already conform to the style; say so plainly rather than implying work wasdone.

Frequently asked questions