metalint
Metalint aggregates multiple frontend linters into a single CLI entrypoint for .NET repositories with Node-based assets. It delegates to ESLint, Stylelint, HTMLHint, and similar tools while keeping their configs explicit and reviewable under `.metalint/`. Use it when your repo already has multiple linters and needs orchestration, not when a single tool like Biome covers your needs.
Metalint provides a unified CLI command to orchestrate multiple frontend linters like ESLint, Stylelint, and HTMLHint in .NET repositories.
AI-generated summary based on this skill's SKILL.md
Install
managedcode/dotnet-skills/metalint · repository language: C#
git clone https://github.com/managedcode/dotnet-skills
cp -r dotnet-skills/catalog/Tools/Metalint/skills/metalint ~/.claude/skills/metalintnpx skillfed install managedcode/dotnet-skills/metalintFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How to run multiple linters in one command with metalint?
Metalint provides a single CLI entrypoint that orchestrates ESLint, Stylelint, HTMLHint, and other frontend linters together. Install the npm package, configure each linter under `.metalint/`, then run `metalint` to execute all of them in sequence. This eliminates the need to chain multiple npm scripts or remember separate commands for each tool.
What is metalint and when should I use it?
Metalint aggregates multiple frontend linters into one unified CLI for .NET repositories with Node-based assets. Use it when your repo already has ESLint, Stylelint, and HTMLHint configured separately and you need orchestration. If a single tool like Biome covers all your linting needs, metalint adds unnecessary complexity.
How does metalint integrate into .NET CI/CD pipelines?
Metalint runs as an npm package within your .NET project's frontend build stage. Add a single `metalint` call to your CI pipeline (GitHub Actions, Azure Pipelines, etc.) instead of invoking each linter separately. This consolidates linting into one step and reduces operational friction across mixed-technology repositories.
Where do I store metalint and linter configurations?
Metalint keeps all linter configs explicit and reviewable under a `.metalint/` directory in your repository root. Each tool (ESLint, Stylelint, HTMLHint) retains its own config file there, making it easy to audit and modify rules without hunting through multiple locations or hidden dotfiles.
Can metalint replace Biome or other unified linters?
Metalint is an orchestrator for existing linters, not a replacement for unified tools like Biome. Choose Biome if you want a single, fast linter covering multiple languages. Choose metalint if you already have ESLint, Stylelint, and HTMLHint running separately and need to consolidate their invocation into one command.
Is metalint open source and what license does it use?
Yes, metalint is open source under the MIT license. This permissive license allows you to use, modify, and distribute it freely in both commercial and personal projects, making it suitable for integration into enterprise .NET and Node repositories.
SKILL.md
rendered from the published skill — quoted content, verbatim
Metalint for Aggregated Frontend Linting in .NET Repositories
Trigger On
- the repo wants one command to run several frontend linters together
- the user asks for a unified lint entrypoint over ESLint, Stylelint, HTMLHint, or similar tools
- the repo already has multiple linters and the problem is orchestration rather than choosing a single owner
Do Not Use For
- simple
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 2 files
catalog/Tools/Metalint/skills/metalint/SKILL.md
catalog/Tools/Metalint/skills/metalint/manifest.json