code-formatter

Automatically formats and validates code files using Prettier and other formatting tools.Use when users mention "format my code", "fix formatting", "apply code style","check formatting", "make code consistent", or "clean up code formatting".Handles JavaScript, TypeScript, JSON, CSS, Markdown, and many other file types.

⭐692stars🔀70forks📁View on GitHub🕐Updated Dec 17, 2025

When & Why to Use This Skill

The Code Formatter Claude skill automates the process of validating and styling code files using industry-standard tools like Prettier. It ensures seamless code consistency across multiple programming and markup languages—including JavaScript, TypeScript, JSON, CSS, and Markdown—helping developers maintain high-quality, readable codebases with minimal manual effort.

Use Cases

  • 1. Project-wide Style Standardization: Automatically apply a unified coding style across an entire repository to ensure consistency among team members and eliminate 'style-only' diffs in pull requests.
  • 2. Automated Code Validation: Use the skill to check for formatting errors and enforce project-specific rules (.prettierrc) before committing code to version control.
  • 3. Legacy Code Cleanup: Quickly reformat inherited or unorganized code files to match current project standards, significantly improving code maintainability.
  • 4. Multi-language Workflow Integration: Streamline the development environment by handling diverse file types like CSS, JSON, and Markdown through a single automated interface.
namecode-formatter
description|
allowed-toolsRead, Write, Edit, Grep, Glob, Bash(cmd:*)
version1.0.0
authorJeremy Longshore <jeremy@intentsolutions.io>
licenseMIT

Code Formatter

Overview

This skill provides automated assistance for the described functionality.

Prerequisites

  • Node.js and npm/npx installed
  • Prettier available globally or locally
  • Write permissions for target files
  • Supported file types in the project

Instructions

  1. Analyze current formatting (prettier --check) and identify files to update.
  2. Configure formatting rules (.prettierrc, .editorconfig) for the project.
  3. Apply formatting (prettier --write) to the target files/directories.
  4. Add ignore patterns (.prettierignore) for generated/vendor outputs.
  5. Optionally enforce formatting via git hooks (husky/lint-staged).

See {baseDir}/references/implementation.md for detailed implementation guide.

Output

Error Handling

See {baseDir}/references/errors.md for comprehensive error handling.

Examples

See {baseDir}/references/examples.md for detailed examples.

Resources

  • name: Check formatting
  • name: Enforce formatting
  • ESLint - Linting and code quality
  • Stylelint - CSS/SCSS linting
  • Markdownlint - Markdown style checking