メニュー
.NET version migration assistant. Guides migration between .NET versions (8→9, 9→10, 10→11), nullable reference type adoption, and AOT compatibility preparation. Provides step-by-step checklists and automated detection of breaking changes.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Execute a blueprint by creating a taskforce — a group of agents working in parallel on blueprint steps. Creates the workspace, assigns tasks, monitors progress, reviews completed work, and merges results. Use when the user wants to execute an existing blueprint with multiple agents. Requires a blueprint file from dev-blueprint.
Orchestrates Aspire distributed applications using the Aspire CLI for running, debugging, and managing distributed apps. USE FOR: aspire start, aspire stop, start aspire app, aspire describe, list aspire integrations, debug aspire issues, view aspire logs, add aspire resource, aspire dashboard, update aspire apphost. DO NOT USE FOR: non-Aspire .NET apps (use dotnet CLI), container-only deployments (use docker/podman), Azure deployment after local testing (use azure-deploy skill). INVOKES: Aspire CLI commands (aspire start, aspire describe, aspire otel logs, aspire docs search, aspire add), bash. FOR SINGLE OPERATIONS: Use Aspire CLI commands directly for quick resource status or doc lookups.
ALWAYS use this skill when investigating API performance, endpoint latency, or trace analysis. This skill provides the exact Aspire CLI commands and span pattern knowledge needed to diagnose N+1 queries, excessive storage reads, duplicate aggregate rehydration, and missing projections. You MUST consult this skill whenever the user mentions: slow endpoints, high latency, too many spans, N+1 patterns, storage reads, trace analysis, span counts, projection vs factory performance, before/after performance comparison, profiling requests, or asks 'why is this slow'. Even if you think you can handle it directly, this skill contains project-specific trace patterns and CLI commands you don't know without it.
Security checklist for C#/.NET backend (ASP.NET Core, EF Core, Event Sourcing). Covers secrets management, input validation, SQL injection, authentication, authorization, rate limiting, security headers, sensitive data handling, Problem Details (RFC 7807), and event sourcing security. Invoked via /dev-security (unified entry point) — not directly.
Security checklist for Angular/TypeScript frontend. Covers XSS prevention, client-side validation, secure authentication patterns, CSRF handling, content security policy, and sensitive data in bundles. Invoked via /dev-security (unified entry point) — not directly.
Test-driven development workflow for C#/.NET using xUnit, NSubstitute, and event sourcing (EventSourcing). Covers aggregate testing, specification testing, projection testing, and proper test isolation. Invoked via /dev-tdd (unified entry point) — not directly.
| version | 1.0.0 |
| name | dev-dotnet-migrate |
| description | .NET version migration assistant. Guides migration between .NET versions (8→9, 9→10, 10→11), nullable reference type adoption, and AOT compatibility preparation. Provides step-by-step checklists and automated detection of breaking changes. |
| disable-model-invocation | true |
| user-invocable | true |
| context | fork |
| argument-hint | [8-to-9 | 9-to-10 | 10-to-11 | nullable | aot] |
Guides incremental migration between .NET versions with breaking change detection and verification.
Stack: C#/.NET (ASP.NET Core, EF Core, NuGet)
Migrate incrementally. One project at a time, verify at each step. Never upgrade the entire solution in one commit. Build confidence through small, verified steps.
| Argument | Action |
|---|---|
8-to-9 | Read references/migrate-dotnet8-to-9.md — .NET 8 LTS → .NET 9 STS |
9-to-10 | Read references/migrate-dotnet9-to-10.md — .NET 9 STS → .NET 10 LTS |
10-to-11 | Read references/migrate-dotnet10-to-11.md — .NET 10 LTS → .NET 11 STS |
nullable | Read references/nullable-references.md — adopt <Nullable>enable</Nullable> |
aot | Read references/aot-compatibility.md — prepare for Native AOT |
| (none) | Detect current version, suggest target, show pre-migration checklist |
These apply to every .NET version upgrade:
[ ] All tests passing on current version
[ ] Dependencies checked for target version support
[ ] Binlog baseline captured (dotnet build /bl:baseline.binlog)
[ ] Git branch created for migration
[ ] CI pipeline supports new SDK version
1. UPDATE SDK → global.json → new SDK version
2. TARGET FRAMEWORK → <TargetFramework>net{version}</TargetFramework> in csproj
3. PACKAGES → Update all Microsoft.* packages to matching version
4. BUILD → dotnet build 2>&1 | tee build-output.txt
5. FIX ERRORS → Address compiler errors from breaking changes
6. TEST → dotnet test — fix behavioral changes
7. INFRASTRUCTURE → Update Dockerfile, CI/CD pipeline SDK versions
8. DEPRECATED APIS → dotnet build /p:TreatWarningsAsErrors=true — catch obsolete usage
1. Shared libraries (no project dependencies)
2. Domain / Core projects
3. Infrastructure / Data access
4. Application / Service layer
5. API / Web host
6. Test projects (last — they depend on everything)
After each project: dotnet build the entire solution to catch cross-project breaks.
# Current SDK
dotnet --version
# Current target frameworks
grep -rh '<TargetFramework>' --include="*.csproj" . | sort -u
# Global.json SDK pin
cat global.json 2>/dev/null || echo "No global.json (using latest installed SDK)"
# Installed SDKs
dotnet --list-sdks
After completing the migration, run the full verification loop:
dotnet build — clean compiledotnet test — all tests passdotnet build /bl:post-migration.binlog — capture for comparisondev-verification-backend --full for comprehensive checksIf migration fails and can't be fixed in reasonable time:
# Revert all migration changes
git checkout -- .
# Or selectively revert
git checkout -- global.json
git checkout -- '*.csproj'
dotnet restore