dotnet-metalint

Orchestrate ESLint, Stylelint, and HTMLHint from a single .NET entrypoint.

8|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/Postpartum-genushyacinthus29/dotnet-skills --skill dotnet-metalint
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-metalint
Source: https://github.com/Postpartum-genushyacinthus29/dotnet-skills/tree/main/skills/dotnet-metalint
Command: npx skills add https://github.com/Postpartum-genushyacinthus29/dotnet-skills --skill dotnet-metalint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Metalint orchestration for .NET repos that ship Node-based frontend assets, providing a single CLI entrypoint to run ESLint, Stylelint, HTMLHint, and related checks via a centralized .metalint/ config.

Core Features & Use Cases

  • Unified frontend lint entrypoint across multiple linters (ESLint, Stylelint, HTMLHint) controlled from a single wrapper.
  • Keeps per-tool configs intact while enabling consistent CI lint steps and easier onboarding.
  • Use Case: teams with mixed .NET backends and frontend assets can run all frontend quality checks with one command.

Quick Start

Initialize Metalint in the repository and run the unified lint command to validate ESLint, Stylelint, and HTMLHint with a single entrypoint.

Frequently Asked Questions about dotnet-metalint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run multiple frontend linters from a single .NET build command?▼

Unified frontend linting under a .NET entrypoint wraps ESLint, Stylelint, and HTMLHint into a single CLI command, using a centralized .metalint/ config to provide clear ownership and consistent CI lint steps.

What is the best way to unify ESLint and Stylelint configurations for CI in a .NET repository?▼

A wrapper config under .metalint/ unifies ESLint, Stylelint, and HTMLHint execution, keeping per-tool configs intact while enabling consistent CI lint steps and easier onboarding for .NET repos with Node-based frontend assets.

Can I run frontend lint checks without altering my existing ESLint and Stylelint config files?▼

Yes, this orchestration approach keeps per-tool configs intact while running ESLint, Stylelint, and HTMLHint via a centralized wrapper, ensuring existing frontend quality configurations remain untouched.

How do I set up a unified lint workflow for Node-based frontend assets in a .NET project?▼

Initialize the orchestration wrapper in the repository to create a .metalint/ config, then run the unified lint command to validate ESLint, Stylelint, and HTMLHint through a single .NET entrypoint.

Does a unified frontend lint wrapper provide clear configuration ownership for CI pipelines?▼

Yes, centralizing wrapper config requirements under .metalint/ provides clear ownership and CI-ready outputs, ensuring consistent frontend quality checks across ESLint, Stylelint, and HTMLHint for .NET repos.