mirror of
https://github.com/dotnet/skills.git
synced 2026-09-20 09:49:54 +08:00
Amaury Levé
460a01882f
* fix: validate native Codex plugin support Separate Codex-compatible plugin components from GitHub Copilot custom agents, validate Codex manifest fields and MCP shapes, and document the native agent installation boundary. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * fix: strengthen Codex plugin verification Validate Codex MCP per-tool settings and add a pinned native smoke lane that installs the marketplace, discovers skills and MCP, and calls binlog_overview. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * fix: avoid restarting Codex MCP smoke client Use the real tool call as the app-server initialization so the Linux smoke test does not start and tear down a redundant status client first. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * fix: harden Codex validation and smoke cleanup Constrain smoke artifacts to a dedicated child directory, validate Codex manifest field shapes and required skill paths, and document the separate Agents SDK handoff model. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * fix: align Codex smoke and hooks parsing Use the clean Codex installation's default provider for the direct MCP call and reject heterogeneous hooks arrays like the runtime parser. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * fix: verify every Codex plugin skill Compare native skill discovery with the full repository inventory, match Codex lexical path rejection, and allow null optional MCP tool settings. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * fix: address Codex compatibility review Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
dotnet-test-migration
Skills and a GitHub Copilot orchestrator agent for migrating .NET test frameworks and platforms. Covers framework version upgrades (MSTest, xUnit), cross-framework conversion (xUnit/NUnit → MSTest), and test platform migration (VSTest → Microsoft.Testing.Platform).
When to use this plugin
- Upgrade MSTest — MSTest v1/v2 → v3, then v3 → v4 (handles source and behavioral breaking changes)
- Upgrade xUnit — xUnit.net v2 → v3
- Convert xUnit to MSTest — port xUnit (v2 or v3) projects to MSTest v4
- Convert NUnit to MSTest — port NUnit (v3 or v4) projects to MSTest v4
- Adopt Microsoft.Testing.Platform — migrate from the VSTest runner to MTP
- Orchestrate migrations — auto-detect the current framework/version/platform and route to the right migration
Skills
| Skill | Description |
|---|---|
| migrate-mstest-v1v2-to-v3 | Upgrade MSTest v1 (assembly refs) or v2 (NuGet 1.x–2.x) to v3 |
| migrate-mstest-v3-to-v4 | Upgrade MSTest v3 to v4 — handles all source and behavioral breaking changes |
| migrate-xunit-to-xunit-v3 | Upgrade xUnit.net v2 to v3 |
| migrate-xunit-to-mstest | Convert xUnit.net (v2 or v3) test projects to MSTest v4 — attributes, assertions, fixtures, lifecycle, output, parallelization |
| migrate-nunit-to-mstest | Convert NUnit (v3 or v4) test projects to MSTest v4 — constraints, data sources, fixture lifecycle, namespace setup, output, parallelization |
| migrate-vstest-to-mtp | Migrate from the VSTest runner to Microsoft.Testing.Platform |
Agents
The agent below is a GitHub Copilot .agent.md definition. Codex plugin installs expose the
migration skills, but not this agent or its static handoff.
| Agent | Purpose |
|---|---|
| test-migration | Auto-detects framework/version/platform and routes to the correct migration skill; coordinates multi-step migrations (e.g., MSTest v1 → v3 → v4) |
Related plugins
- dotnet-test — running, generating, and analyzing tests; testability improvement; coverage. The migration skills here reference shared
dotnet-testskills by name (e.g.,platform-detectionfor framework/platform detection,writing-mstest-testsfor idiomatic MSTest polish, andrun-testsfor verification). Installdotnet-testalongside this plugin to get the full workflow.
Prerequisites
- .NET SDK installed (
dotneton PATH) - A project with an existing test framework (MSTest, xUnit, NUnit, or TUnit)