What problem does it solve? Upgrading a .NET test project from MSTest v1 (assembly references) or v2 (NuGet 1.x-2.x) to MSTest v3 introduces breaking changes such as removed assertion overloads, strict DataRow type matching, dropped target frameworks, and unsupported .testsettings files, causing build errors and silently ignored configuration. ## Core Features & Use Cases - Version Detection and Assessment: Identifies whether a project uses MSTest v1 assembly references or v2 NuGet packages before recommending migration steps. - Breaking Change Resolution: Provides concrete before/after fixes for Assert.AreEqual generic overloads, DataRow strict type matching, timeout behavior, and target framework updates. - Configuration Migration: Replaces .testsettings with equivalent .runsettings and supports adopting the MSTest metapackage or MSTest.Sdk. - Use Case: After bumping MSTest.TestFramework from 2.2.10 to 3.8.0, a project fails to compile with Assert.AreEqual overload errors; this Skill walks through each error and applies the correct generic-type fix. ## Quick Start Migrate my test project from MSTest v2 to MSTest v3 and fix any build errors that appear.