formatter-linter-expert

Universal code formatter and linter analyzer for multi-ecosystem projects (Laravel/PHP, Bun/Node/TS/JS, React, Vue, Astro, Nuxt, Go, Rust, Deno) with intelligent asdf version management, auto-detection, and interactive workflows

2starsUpdated 4/3/2026

Data Science & ML #go #code-linting #laravel #code-formatting #nodejs #python

Security Assessment

Critical Risk(25/100)

Detected risks:

Persistence([README.md] .bashrc, [SKILL.md] .bashrc)

Remote Code Execution([README.md] curl -fsSL https://deno.land/install.sh | sh)

Security Score25/100

About formatter-linter-expert

The formatter-linter-expert is a comprehensive tool designed to streamline the code formatting and linting process across multiple development ecosystems. It automatically detects the ecosystem your project belongs to (such as Laravel, Node, Go, Rust, Deno, and more), ensuring that the correct tool versions and configurations are used. By integrating with asdf version manager, it ensures consistency in tooling, especially when different environments or versions are required for different projects. The skill allows developers to quickly analyze, format, and lint code with minimal configuration, making it an ideal solution for multi-ecosystem codebases.

FAQ

How does the formatter-linter-expert detect my project ecosystem?

The skill detects your project ecosystem by searching for file markers such as `composer.json` for Laravel, `package.json` for Node/Bun/React/Vue, `go.mod` for Go, `Cargo.toml` for Rust, and `deno.json` for Deno. It will also check for an existing `.tool-versions` file to integrate with asdf for version management.

Do I need to install ecosystem-specific tools before using the skill?

Yes, the skill requires ecosystem-specific tools to be installed, such as `pint` for Laravel/PHP, `prettier` and `eslint` for Node/JavaScript/TypeScript, `goimports` and `golangci-lint` for Go, and others. These tools can be installed via package managers like Composer, NPM, or Go.

Can I customize the configuration files for each ecosystem?

Yes, the skill will attempt to auto-detect configuration files like `.prettierrc`, `.eslintrc`, or `phpstan.neon`. If the files are not found, you can provide custom configuration file paths, or the skill will fall back to its default configurations.

What happens if I choose 'Analyze Only' mode?

In 'Analyze Only' mode, the skill generates a detailed report of the codebase without making any modifications to the files. This mode is ideal for code reviews, CI/CD pipeline integration, or an initial assessment of the code quality.

What are the prerequisites for using this skill?

The skill requires Python 3.9+ for running the scripts. Ecosystem-specific tools must also be installed, and it is recommended to use the asdf version manager for handling tool versions. A `.tool-versions` file in your project root is optional but recommended.