What problem does it solve? After editing code, files often drift from the project's configured code style, causing noisy diffs and inconsistent formatting. This Skill reformats source files using the project's own style settings, either through the running IntelliJ IDE or through the project's configured external formatter when the IDE is unreachable. ## Core Features & Use Cases - IDE-driven formatting: Routes formatting through IntelliJ's ReformatCodeProcessor via the Steroid MCP tools, keeping the IDE's VFS/PSI caches consistent and matching exactly what developers see in the editor. - CLI fallback: When the IDE is unreachable, detects and runs the project's own formatter (Spotless via Gradle/Maven, or a google-java-format / palantir-java-format JAR) so output still follows the committed style configuration. - Flexible scopes: Formats a single named file, a specific line range or code block (IDE only), a group of named files, or all uncommitted git-changed files, then reports the actual diff. - Use Case: After an AI assistant edits several Java files, invoke this Skill to reformat just those changed files so the result conforms to the project's Spotless configuration before committing. ## Quick Start Reformat all my uncommitted files using the project's code style and show me what changed.