ManagedCode dotnet-skills
Overview
Use this skill when a .NET project needs an installable skill catalog or CLI-oriented agent workflow from managedcode/dotnet-skills. The upstream repository targets Codex, Claude Code, GitHub Copilot, and Gemini.
Compatibility: .NET, C#, CLI-based skill installation, migration workflows, and multi-agent coding assistants.
Workflow
- Inspect the solution structure, SDK version, package centralization, test framework, and CI before choosing any upstream skill.
- For migration tasks, classify the migration target first: framework upgrade, library replacement, Azure migration, architecture modernization, or test modernization.
- Use the upstream catalog as a reference, then adapt instructions to the local repository conventions.
- Validate with
dotnet restore, dotnet build, and the narrowest relevant dotnet test command.
- Capture migration decisions in a short compatibility note covering breaking changes and remaining manual work.
Guardrails
- Do not install or execute upstream CLI tooling without checking the README and local project constraints.
- Treat generated migration output as a draft until tests prove behavior parity.
- Preserve nullable context, analyzers, editorconfig rules, and package versioning strategy.
- Keep source and generated migration artifacts separated when experimenting.
Expected Output
Return a migration or implementation checklist, commands, validation evidence, and any upstream skill or CLI reference used.
1---2name: managedcode-dotnet-skills3description: Use ManagedCode dotnet-skills for installable .NET agent skills, CLI workflows, and migration-oriented guidance.4license: MIT5---67# ManagedCode dotnet-skills89## Overview1011Use this skill when a .NET project needs an installable skill catalog or CLI-oriented agent workflow from [managedcode/dotnet-skills](https://github.com/managedcode/dotnet-skills). The upstream repository targets Codex, Claude Code, GitHub Copilot, and Gemini.1213Compatibility: .NET, C#, CLI-based skill installation, migration workflows, and multi-agent coding assistants.1415## Workflow16171. Inspect the solution structure, SDK version, package centralization, test framework, and CI before choosing any upstream skill.182. For migration tasks, classify the migration target first: framework upgrade, library replacement, Azure migration, architecture modernization, or test modernization.193. Use the upstream catalog as a reference, then adapt instructions to the local repository conventions.204. Validate with `dotnet restore`, `dotnet build`, and the narrowest relevant `dotnet test` command.215. Capture migration decisions in a short compatibility note covering breaking changes and remaining manual work.2223## Guardrails2425- Do not install or execute upstream CLI tooling without checking the README and local project constraints.26- Treat generated migration output as a draft until tests prove behavior parity.27- Preserve nullable context, analyzers, editorconfig rules, and package versioning strategy.28- Keep source and generated migration artifacts separated when experimenting.2930## Expected Output3132Return a migration or implementation checklist, commands, validation evidence, and any upstream skill or CLI reference used.
autohandai