C# and .NET Engineering Profile
Use this profile only after repository discovery identifies the stack. Read focused checks when .NET-specific gates or hazards determine the result.
Workflow
- Discover solution and project files,
global.json, central package configuration, NuGet settings, lockfiles, target frameworks, runtime identifiers, and repository scripts.
- Follow repository-defined commands and pinned SDK or tool versions before suggesting defaults.
- Review material hazards, especially sync-over-async, lost cancellation,
async void, disposal and lifetime errors, nullable-reference gaps, dependency-injection scope mismatches, deferred LINQ behavior, and unsafe serialization.
- When data access is present, review Entity Framework tracking, query shape, client evaluation, concurrency, transactions, provider behavior, and migration authority.
- Select proportionate gates from repository formatting, analyzers, compilation, tests, package validation, builds, and dependency review.
- Review compatibility across target frameworks, SDK selection, package graphs, public APIs, trimming or native AOT, operating systems, and database providers.
- Report every missing tool, skipped command, unsupported platform, or unavailable environment as incomplete rather than passing.
Boundaries
- Repository scripts and tests run code, and dependency checks can contact registries. Run a gate only when the user asked for checks and trusts the repository. Otherwise, name it as the next safe gate.
- Do not invent one universal
dotnet command or replace repository policy with generic preferences.
- Do not restore from an unapproved feed, install tools, update packages, apply a database migration, publish, deploy, or mutate shared state merely to run a gate.
- Separate static review, executed checks, build evidence, migration evidence, provider state, and live behavior.
Output
Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.
Return Discovery, Hazards, Commands selected, Results, Compatibility, Missing evidence, and Next safe gate.
Example
Synthetic example; not an observed client result.
Input: An ASP.NET handler blocks on Task.Result inside an async request.
Output: warning: synchronous waiting may block request threads. Inspect the call chain and cancellation behavior; validate an async change with repository tests.
1---2name: stack-csharp-dotnet3description: "Reviews C# and .NET changes when ASP.NET, Entity Framework, async code, packages, or target frameworks need focused checks; follows repository SDK and build contracts."4license: MIT5metadata:6 source: https://skillmd.com/skills/jovanipink/stack-csharp-dotnet7 author: "Measured Studios"8 version: "0.19.0"9 plugin: "measured-stacks"10 invocation: "implicit"11 provenance: "original"12 risk_class: "read-only"13---1415# C# and .NET Engineering Profile1617Use this profile only after repository discovery identifies the stack. Read [focused checks](references/checks.md) when .NET-specific gates or hazards determine the result.1819## Workflow20211. Discover solution and project files, `global.json`, central package configuration, NuGet settings, lockfiles, target frameworks, runtime identifiers, and repository scripts.222. Follow repository-defined commands and pinned SDK or tool versions before suggesting defaults.233. Review material hazards, especially sync-over-async, lost cancellation, `async void`, disposal and lifetime errors, nullable-reference gaps, dependency-injection scope mismatches, deferred LINQ behavior, and unsafe serialization.244. When data access is present, review Entity Framework tracking, query shape, client evaluation, concurrency, transactions, provider behavior, and migration authority.255. Select proportionate gates from repository formatting, analyzers, compilation, tests, package validation, builds, and dependency review.266. Review compatibility across target frameworks, SDK selection, package graphs, public APIs, trimming or native AOT, operating systems, and database providers.277. Report every missing tool, skipped command, unsupported platform, or unavailable environment as incomplete rather than passing.2829## Boundaries3031- Repository scripts and tests run code, and dependency checks can contact registries. Run a gate only when the user asked for checks and trusts the repository. Otherwise, name it as the next safe gate.32- Do not invent one universal `dotnet` command or replace repository policy with generic preferences.33- Do not restore from an unapproved feed, install tools, update packages, apply a database migration, publish, deploy, or mutate shared state merely to run a gate.34- Separate static review, executed checks, build evidence, migration evidence, provider state, and live behavior.3536## Output3738Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.3940Return Discovery, Hazards, Commands selected, Results, Compatibility, Missing evidence, and Next safe gate.4142## Example4344Synthetic example; not an observed client result.4546Input: An ASP.NET handler blocks on Task.Result inside an async request.4748Output: warning: synchronous waiting may block request threads. Inspect the call chain and cancellation behavior; validate an async change with repository tests.