dotnet-eslint

Integrate ESLint as a configurable lint gate for .NET frontend assets.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a configurable ESLint-based lint gate for .NET projects that include JavaScript, TypeScript, or other frontend assets, ensuring consistent frontend quality across the repo.

Core Features & Use Cases

  • Integrates ESLint config and plugins into .NET projects with frontend code
  • Offers repo-local scripts for linting and autofixing (lint, lint:fix) and clear guidance for CI integration
  • Guides bootstrap and maintenance when frontend tooling is present or missing, with safe defaults for typical .NET frontend folders

Quick Start

Run the lint gate in your .NET repository by enabling the ESLint workflow provided by this skill and executing the lint script to begin front-end quality enforcement.

Frequently Asked Questions about dotnet-eslint

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

FAQPage Schema
How do I run ESLint in a .NET repository with frontend code?

To run ESLint in a .NET repository, you enable the provided ESLint workflow and execute the lint script. This enforces frontend code quality across JavaScript, TypeScript, or React assets within your .NET project structure.

Can I integrate ESLint into a .NET CI pipeline to enforce frontend lint findings?

Yes, you can integrate ESLint into .NET CI pipelines to enforce frontend lint findings. The skill provides clear guidance for CI integration and offers repo-local scripts to apply automated lint checks against your frontend assets.

Do I need a package.json and ESLint configuration to enforce frontend lint in .NET repos?

Yes, you need a .NET repository with a frontend folder structure containing package.json and an ESLint configuration file like eslint.config.* or .eslintrc*. These files are required to enable automated lint checks.

What is the best way to autofix frontend lint issues in a .NET project?

The best way to autofix frontend lint issues in a .NET project is by running the lint:fix script provided by the skill. This script automatically applies ESLint fixes to maintain frontend code quality.

Does this ESLint integration work with TypeScript and React assets inside .NET projects?

Yes, this ESLint integration works with TypeScript, React, and other Node-based frontend assets inside .NET projects. It applies safe defaults for typical .NET frontend folders to ensure consistent quality.