eslint
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.
ESLint for Frontend Assets in .NET Repositories sets up JavaScript and TypeScript linting for .NET projects with Node-based frontend code.
AI-generated summary based on this skill's SKILL.md
Install
managedcode/dotnet-skills/eslint · repository language: C#
git clone https://github.com/managedcode/dotnet-skills
cp -r dotnet-skills/catalog/Tools/ESLint/skills/eslint ~/.claude/skills/eslintnpx skillfed install managedcode/dotnet-skills/eslintFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I set up ESLint for .NET JavaScript frontend?
ESLint is a static analysis tool that enforces code quality in JavaScript and TypeScript. To set up ESLint for your .NET JavaScript frontend, install it locally via npm or yarn in your frontend directory, create an .eslintrc configuration file specifying your environment (browser, Node.js, or both), and define which rule sets to extend (e.g., eslint:recommended). For .NET repos with package.json, ESLint integrates alongside your existing build tools and can be invoked via npm scripts or CI/CD pipelines.
What is the process to lint TypeScript in ASP.NET Core?
ESLint supports TypeScript through the @typescript-eslint parser and plugin. To lint TypeScript in ASP.NET Core, install @typescript-eslint/eslint-plugin and @typescript-eslint/parser, update your .eslintrc to specify the TypeScript parser, and add typescript-eslint rules to your configuration. Point ESLint at your .ts and .tsx files using glob patterns in your lint command, then integrate the command into your ASP.NET build or CI/CD workflow for automated validation.
How do I configure ESLint React rules?
ESLint React rules configuration requires the eslint-plugin-react package. Install it, then add 'react' to the plugins array in your .eslintrc and enable recommended rules via extends: ['plugin:react/recommended']. Configure React-specific settings like the JSX pragma and version detection. For TypeScript React projects, combine this with @typescript-eslint and eslint-plugin-react-hooks to enforce best practices for hooks and component patterns.
Can ESLint automatically fix JavaScript errors?
Yes, ESLint includes an auto-fix feature. Run eslint --fix on your source files to automatically correct many common issues like formatting, unused variables, and import ordering. Not all rules support auto-fix; some require manual intervention. Use --fix in your development workflow or pre-commit hooks, and integrate it into CI/CD to catch and repair issues before they reach production.
How do I integrate ESLint into my CI/CD pipeline?
ESLint integrates into CI/CD by adding a lint step to your pipeline configuration (GitHub Actions, Azure Pipelines, etc.). Install ESLint and dependencies in your build environment, run eslint with a glob pattern targeting your frontend source files, and fail the build if violations exceed your threshold. Store your .eslintrc in version control so all environments use consistent rules. This ensures frontend code quality is validated on every commit or pull request.
What does ESLint ignore patterns and scoping do?
ESLint ignore patterns prevent linting of specified files and directories. Use an .eslintignore file or the ignorePatterns property in .eslintrc to exclude node_modules, build outputs, and generated files. Scoping rules to specific file types (e.g., .js, .ts, .jsx) via overrides in your config lets you apply different rule sets to different parts of your codebase, such as stricter rules for source files and relaxed rules for test files.
SKILL.md
rendered from the published skill — quoted content, verbatim
ESLint for Frontend Assets in .NET Repositories
Trigger On
- the repo has
package.json,eslint.config.*,.eslintrc*,tsconfig.json, or JS/TS/React frontend files - the user asks for JavaScript or TypeScript linting, React rule enforcement, import hygiene, or unsafe frontend patterns
- CI should fail on frontend lint findings instead of relying on editor-only feedback
Do Not Use For
- CSS ownership by itself; route that to
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 2 files
catalog/Tools/ESLint/skills/eslint/SKILL.md
catalog/Tools/ESLint/skills/eslint/manifest.json