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
Decision gist · record as of 2026-07-25
Metalint provides a unified CLI command to orchestrate multiple frontend linters like ESLint, Stylelint, and HTMLHint in .NET repositories. 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.
Use it when
- Metalint aggregates multiple frontend linters into one unified CLI for .NET repositories with Node-based assets.
- Metalint runs as an npm package within your .NET project's frontend build stage.
Verify before relying
Read SKILL.md below before installing (2 files). Open directory: indexed for reading, not audited.
Install
managedcode/dotnet-skills/metalint · repository language: C#
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently 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)
File tree — 2 files
catalog/Tools/Metalint/skills/metalint/SKILL.md
catalog/Tools/Metalint/skills/metalint/manifest.json
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Set up a single CLI command to run multiple frontend linters”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
This skill configures ESLint to lint JavaScript, TypeScript, and React code in .NET repositories that include frontend assets. It detects existing configurations, installs dependencies locally, and establishes repeatable lint commands in your build pipeline. Use it when your repo has package.json, frontend source files, or explicit linting requests.
htmlhint enforces HTML structure and attribute correctness on static files and built output in .NET repositories. Target rendered HTML in folders like wwwroot/ or dist/ rather than raw server-side templates, keeping validation separate from JavaScript and full-site audits.
Stylelint brings CSS and SCSS linting to .NET projects that bundle stylesheets alongside web frontends. Set up repo-local configuration, define clear ownership boundaries, and enforce naming conventions and duplicate-style cleanup without conflicting with other linters.
sonarjs integrates SonarJS-derived rules into ESLint for .NET repositories shipping JavaScript or TypeScript frontends. It surfaces cognitive complexity limits, bug-prone patterns, and maintainability issues beyond baseline linting, supporting both local developer workflows via eslint-plugin-sonarjs and server-side SonarQube or SonarCloud gates.
Biome integrates into .NET repositories to provide combined formatting, linting, and import organization across JavaScript, TypeScript, CSS, JSON, GraphQL, and HTML. The skill handles ownership decisions between Biome and existing tools like ESLint or Prettier, generates configuration, and establishes repeatable commands for CI and local development. It guides migration strategies and validates that your build and test flows remain stable after changes.
webhint runs runtime audits against .NET browser-facing sites, catching accessibility, performance, security header, SEO, and PWA issues that static linters miss. Configure a `.hintrc` baseline, point it at your local or deployed URL, and get categorized findings ready for the team to act on.
More skills chous (MIT)