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

Workflow

1. Define underlying ownership first:

- ESLint for JS or TS - Stylelint for CSS or SCSS - HTMLHint for static HTML - other delegated linters only when the repo really uses them

1. Use Metalint only after those owners are explicit.
2. Keep all wrapper configuration under .metalint/ and keep the delegated configs reviewable.
3. Add package scripts such as:

- lint: metalint - lint:fix: metalint --fix

1. Treat formatter overlap carefully. If delegated tools can all fix files, define which ones are allowed to mutate which globs.
2. Use Metalint in CI when the repo benefits from a single frontend lint step and formatter output such as GitHub annotations.
3. Re-run the underlying owners directly when debugging Metalint issues so failures stay attributable.

Deliver

• one repeatable frontend lint entrypoint
• explicit delegated-tool ownership
• wrapper config that stays readable and attributable

Validate

• each delegated linter is actually installed and configured
• fix ownership is explicit across file types
• CI output remains attributable to the right underlying tool
• Metalint reduced operational friction instead of hiding the real owners

Related skills

Related agents