skills.rest
michaelvolz
michaelvolzCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

rm-guide-warnings

Enforce zero-warning builds and govern pragma suppressions in dotnet code.

Updated Nov 11, 2023
Search Tags:#dotnet#warnings#static-analysis#code-health#analyzer#pragma#build-quality
One-click install
npx skills add https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb --skill rm-guide-warnings
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rm-guide-warnings
Source: https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb/tree/main/.opencode/skills/redmuffin-standards/rm-guide-warnings
Command: npx skills add https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb --skill rm-guide-warnings

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps analyzer warnings from accumulating by insisting on zero-warning builds, preventing teams from hiding issues behind ad hoc suppressions.

Core Features & Use Cases

  • Zero-warning discipline: Target every analyzer and build warning and resolve root causes instead of hiding them.
  • Pragma governance: Treat #pragma warning disable lines as immutable unless explicitly approved and clearly document their justification.
  • Consistent remediation: Apply a single reliable fix for each warning class to stop churn and keep future runs clean.
  • Use Case: While triaging Blazor or backend C# dead code analyzers for a release, log the intended suppressions, and keep the build warning-free.

Quick Start

Guide me through cleaning the analyzer warnings in this pull request by highlighting root causes and reaffirming approved pragmas.

Frequently Asked Questions about rm-guide-warnings

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

FAQPage Schema
How do I enforce zero-warning builds in dotnet to stop analyzer warnings from accumulating?▼

You enforce zero-warning builds by resolving the root cause of every analyzer and build warning rather than hiding it. This approach prevents teams from accumulating hidden issues behind ad hoc suppressions and keeps build quality consistent.

What is the best way to manage existing pragma warning disable suppressions in C#?▼

Treat pragma warning disable lines as immutable unless explicitly approved. You must document the justification for every approved pragma change and solve the underlying root issue before adding or modifying any suppressions.

How do I clean up analyzer warnings in a Blazor codebase before a release?▼

Clean up analyzer warnings by triaging each one to find its root cause and applying a single reliable fix for each warning class. This stops code churn and keeps future analyzer runs clean for your Blazor or backend C# release.

When should I use pragma warning disable instead of fixing dotnet analyzer warnings?▼

Use pragma warning disable only when a suppression is explicitly approved and clearly documented. You must always solve the root issue first, treating pragmas as a last resort to prevent inconsistent analyzer warning handling across your dotnet project.

Related Skills

Explore More Software Engineering Skills→
waynebrantleywaynebrantley
1

build-doctor

Diagnose and fix build errors and warnings in TypeScript and .NET projects.

Community
Advanced
sayedihashimisayedihashimi
2

dotnet-aot-compat

Resolve IL trim and AOT analyzer warnings for .NET Native AOT compatibility.

Community
Advanced
GlourGlour

systematic-debugging

Diagnose technical issues across code, services, and containers using a four-phase workflow.

Community
Advanced
paudleypaudley
6

lint-remediation

Convert static analysis and linting reports into code refactoring instructions.

Community
Intermediate