Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fritzandfriends/analyzer-development
Create Roslyn-based analyzers and code-fix providers for detecting Web Forms migration patterns. Covers DiagnosticAnalyzer architecture, diagnostic ID conventions (BWFC001–BWFC099), CodeFixProvider authoring, testing with CSharpAnalyzerTest/CSharpCodeFixTest, and the analyzer release tracking files.
Passed 18 of 22 test cases with the skill, and 9 of 22 without it.
and 9 more in the full report
9 fixed9 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
What CLI command should I execute to run all unit tests in the analyzer test project while suppressing the standard dotnet banner logo?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies dotnet test src/BlazorWebFormsComponents.Analyzers.Test --nologo | Missed | Passed |
The instructions your model reads when the skill loads.
This skill covers creating Roslyn analyzers and code-fix providers in the BlazorWebFormsComponents.Analyzers project.
The analyzer project ships as a NuGet analyzer package alongside the main BWFC library. Analyzers detect Web Forms patterns in user code and suggest BWFC replacements.
src/BlazorWebFormsComponents.Analyzers/
├── *Analyzer.cs — DiagnosticAnalyzer implementations
├── *CodeFixProvider.cs — Optional companion code-fix providers
├── SyntaxExtensions.cs — Shared Roslyn helper methods
├── AnalyzerReleases.Shipped.md — Released diagnostic IDs
└── AnalyzerReleases.Unshipped.md — In-progress diagnostic IDs
src/BlazorWebFormsComponents.Analyzers.Test/
├── *AnalyzerTests.cs — Analyzer unit tests
├── *CodeFixTests.cs — Code-fix unit tests
└── AllAnalyzersIntegrationTests.cs — Cross-cutting integration tests
| Analyzer | Diagnostic | Detects |
|---|---|---|
EventHandlerSignatureAnalyzer | BWFC001+ | Web Forms event handler signatures |
FindControlUsageAnalyzer | BWFC0xx | FindControl() calls |
IsPostBackUsageAnalyzer | BWFC0xx | IsPostBack property usage |
ViewStateUsageAnalyzer | BWFC0xx | ViewState["key"] access |
ViewStatePropertyPatternAnalyzer | BWFC0xx | ViewState-backed property patterns |
SessionUsageAnalyzer | BWFC0xx | Session["key"] access |
ResponseObjectUsageAnalyzer | BWFC0xx | Response.Redirect, Response.Write |
ResponseRedirectAnalyzer | BWFC0xx | Response.Redirect specifically |
RequestObjectUsageAnalyzer | BWFC0xx | Request.QueryString, Request.Form |
PageClientScriptUsageAnalyzer | BWFC0xx | ClientScript.Register* |
ScriptManagerUsageAnalyzer | BWFC0xx | ScriptManager usage |
RunatServerAnalyzer | BWFC0xx | runat="server" in markup |
test cases passed, vs 9 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.