Code formatter
Skill ComeOnOliver/skillshub/skills/aiskillstore/marketplace/curiouslearner/code-formatter
🧠The right skill, one API call. AI agent skills registry with token-efficient skill resolution. 5,000+ skills from 500+ top repos.
npx -y skills add ComeOnOliver/skillshub --skill code-formatterAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Automatically format code across multiple languages with opinionated configurations.
SKILL.md
1.7 KB, 369 tokens by cl100k_base, as published. Nobody here has run it
Code Formatter Skill
Automatically format code across multiple languages with opinionated configurations.
Instructions
You are a code formatting expert. When invoked:
-
Detect Languages: Identify all code file types in the current directory or specified path
-
Check for Configs: Look for existing formatting configurations (.prettierrc, .editorconfig, pyproject.toml, etc.)
-
Apply Formatting: Format code according to:
- Existing project configuration (if found)
- Language-specific best practices (if no config exists)
- Popular style guides (e.g., PEP 8 for Python, StandardJS, Google Style Guide)
-
Report Changes: Summarize what was formatted and any style decisions made
Supported Languages
- JavaScript/TypeScript (Prettier)
- Python (Black, autopep8)
- Go (gofmt)
- Rust (rustfmt)
- Java (Google Java Format)
- CSS/SCSS/LESS
- HTML
- JSON/YAML
- Markdown
Usage Examples
@code-formatter
@code-formatter src/
@code-formatter --check-only
@code-formatter --language python
Formatting Rules
- Use 2 spaces for JavaScript/TypeScript/CSS
- Use 4 spaces for Python
- Use tabs for Go
- Maximum line length: 100 characters (unless project config specifies otherwise)
- Always use semicolons in JavaScript (unless project uses StandardJS)
- Single quotes preferred for JavaScript (unless project config says otherwise)
- Trailing commas in multi-line structures
Notes
- Always respect existing project configuration files
- Ask before modifying configuration files
- Never format generated code or vendor directories
- Skip binary files and lock files