dotnet/skills
Overview
Use this skill when a .NET or C# repository needs coding-agent guidance from the upstream dotnet/skills project. The upstream repository provides skills and plugins intended to ground agents in .NET development conventions.
Compatibility: .NET, C#, coding-agent plugins, Codex, Claude Code, and GitHub Copilot-style workflows.
Workflow
- Identify the .NET project shape: solution files, SDK version, target frameworks, test projects, analyzers, and package management.
- Read upstream instructions before reusing a plugin or skill because install paths and supported agents may change.
- Use repository-local evidence first:
global.json, .sln, .csproj, Directory.Build.*, Directory.Packages.props, tests, and CI.
- Apply .NET guidance incrementally: restore, build, test, inspect warnings, then change code in small slices.
- For modernization, preserve public contracts, serialization formats, configuration names, and deployment assumptions.
Guardrails
- Do not assume all upstream plugins are installed in the current workspace.
- Keep generated code aligned with the target framework already used by the repository.
- Prefer built-in .NET tooling (
dotnet restore, dotnet build, dotnet test, analyzers) for validation.
- Record unresolved SDK, workload, or package compatibility issues explicitly.
Expected Output
Return a .NET-focused implementation or modernization plan with project evidence, commands run, compatibility notes, and validation results.
1---2name: dotnet-skills3description: Use dotnet/skills for .NET and C# coding-agent guidance, plugins, project analysis, and modernization workflows.4license: MIT5---67# dotnet/skills89## Overview1011Use this skill when a .NET or C# repository needs coding-agent guidance from the upstream [dotnet/skills](https://github.com/dotnet/skills) project. The upstream repository provides skills and plugins intended to ground agents in .NET development conventions.1213Compatibility: .NET, C#, coding-agent plugins, Codex, Claude Code, and GitHub Copilot-style workflows.1415## Workflow16171. Identify the .NET project shape: solution files, SDK version, target frameworks, test projects, analyzers, and package management.182. Read upstream instructions before reusing a plugin or skill because install paths and supported agents may change.193. Use repository-local evidence first: `global.json`, `.sln`, `.csproj`, `Directory.Build.*`, `Directory.Packages.props`, tests, and CI.204. Apply .NET guidance incrementally: restore, build, test, inspect warnings, then change code in small slices.215. For modernization, preserve public contracts, serialization formats, configuration names, and deployment assumptions.2223## Guardrails2425- Do not assume all upstream plugins are installed in the current workspace.26- Keep generated code aligned with the target framework already used by the repository.27- Prefer built-in .NET tooling (`dotnet restore`, `dotnet build`, `dotnet test`, analyzers) for validation.28- Record unresolved SDK, workload, or package compatibility issues explicitly.2930## Expected Output3132Return a .NET-focused implementation or modernization plan with project evidence, commands run, compatibility notes, and validation results.
autohandai