# Csharp Dotnet Engineering Profile

> Apply focused C# and .NET engineering judgment after repository gate discovery. Use for .NET applications, libraries, ASP.NET Core, Entity Framework Core, async behavior, tests, packages, compatibility, and builds; defer exact commands to repository evidence.

- Skill: `jovanipink/csharp-dotnet-engineering-profile` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add jovanipink/csharp-dotnet-engineering-profile`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jovanipink/csharp-dotnet-engineering-profile/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- License: MIT
- Author: JovaniPink (https://skillmd.com/u/jovanipink)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/jovanipink/csharp-dotnet-engineering-profile

---


# C# and .NET Engineering Profile

Use this profile only after repository discovery identifies the stack. Read [focused checks](references/checks.md) when .NET-specific gates or hazards determine the result.

## Workflow

1. Discover solution and project files, `global.json`, central package configuration, NuGet settings, lockfiles, target frameworks, runtime identifiers, and repository scripts.
2. Follow repository-defined commands and pinned SDK or tool versions before suggesting defaults.
3. 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.
4. When data access is present, review Entity Framework tracking, query shape, client evaluation, concurrency, transactions, provider behavior, and migration authority.
5. Select proportionate gates from repository formatting, analyzers, compilation, tests, package validation, builds, and dependency review.
6. Review compatibility across target frameworks, SDK selection, package graphs, public APIs, trimming or native AOT, operating systems, and database providers.
7. Report every missing tool, skipped command, unsupported platform, or unavailable environment as incomplete rather than passing.

## Boundaries

- 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

Return Discovery, Hazards, Commands selected, Results, Compatibility, Missing evidence, and Next safe gate.