dotnet-sonarjs

Apply SonarJS-derived ESLint rules to JavaScript and TypeScript frontend assets in .NET repositories.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams enforce deeper quality checks in .NET projects that host JavaScript or TypeScript frontends by applying SonarJS-derived rules to frontend code.

Core Features & Use Cases

  • Applies eslint-plugin-sonarjs rules to JavaScript/TypeScript frontend assets in a .NET repository to identify bugs, code smells, and cognitive complexity beyond a minimal ESLint baseline.
  • Supports integration with existing CI pipelines using SonarQube or SonarCloud, as well as local developer workflows.
  • Useful for teams upgrading from basic ESLint tuning to Sonar-based quality gates in polyglot stacks.

Quick Start

Install and configure eslint-plugin-sonarjs in your project and align the Sonar rules with your CI pipeline to begin enhanced frontend analysis.

Frequently Asked Questions about dotnet-sonarjs

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

FAQPage Schema
How do I enforce SonarJS rules on JavaScript and TypeScript frontend assets in a .NET repository?

You can enforce SonarJS rules by applying eslint-plugin-sonarjs to your JavaScript and TypeScript frontend assets within the .NET repository. This identifies bug risks, code smells, and cognitive complexity beyond a minimal ESLint baseline.

What is the benefit of using SonarJS rules for frontend code quality in polyglot .NET stacks?

SonarJS rules offer deeper bug-risk, code-smell, and cognitive-complexity checks for JavaScript and TypeScript frontend code. This allows polyglot .NET teams to upgrade from basic ESLint tuning to comprehensive Sonar-based quality gates.

Can I integrate eslint-plugin-sonarjs with existing SonarQube or SonarCloud CI pipelines?

Yes, eslint-plugin-sonarjs integrates with existing SonarQube or SonarCloud CI pipelines. It aligns local developer workflows with your CI quality gates to ensure continuous frontend code analysis.

Do I need a local ESLint setup to apply Sonar-derived rules to my .NET frontend project?

Yes, applying SonarJS-derived rules relies on an existing local ESLint setup in your project. You must install and configure eslint-plugin-sonarjs locally before aligning it with your CI pipeline.

How do I upgrade from basic ESLint to Sonar-based quality gates for TypeScript in .NET?

To upgrade from basic ESLint to Sonar-based quality gates, install and configure eslint-plugin-sonarjs in your project. Align the Sonar rules with your CI pipeline to begin enhanced frontend analysis for TypeScript assets.