dotnet-retarget-review-gate

Enumerate .NET TFMs and update references across apps, tests, and packaging.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/BSchafer01/PanelNester --skill dotnet-retarget-review-gate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-retarget-review-gate
Source: https://github.com/BSchafer01/PanelNester/tree/main/.squad/skills/dotnet-retarget-review-gate
Command: npx skills add https://github.com/BSchafer01/PanelNester --skill dotnet-retarget-review-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gates repo-wide .NET target framework changes to prevent hidden TFM dependencies from causing build, test, and packaging failures.

Core Features & Use Cases

  • Enumerates all authored projects with TFMs and creates exact replacement mappings, including Windows-specific netX variants.
  • Validates and updates hardcoded TFMs in tests, documentation, and project files to keep the solution consistent after retargeting.
  • Verifies desktop apps keep Windows-specific TFMs and settings like UseWPF, and re-runs baseline checks to ensure packaging and test suites pass.

Quick Start

Retarget a repo-wide .NET solution by enumerating every netX TFM and applying the exact replacements across apps, tests, and packaging.

Frequently Asked Questions about dotnet-retarget-review-gate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I retarget a .NET solution without breaking hidden TFM dependencies?

To safely retarget a .NET solution, enumerate all authored projects with TFMs and create exact replacement mappings across apps, unit tests, and packaging to prevent hidden TFM dependencies from causing build failures.

What happens to hardcoded TFMs in tests and docs when changing a .NET target framework?

When changing a .NET target framework, you must validate and update hardcoded TFMs in tests, documentation, and project files to maintain solution consistency after retargeting.

Do I need to update Windows-specific settings like UseWPF when retargeting desktop apps?

Yes, when retargeting desktop apps you must verify that Windows-specific TFMs and settings like UseWPF are retained to ensure the WPF application continues building correctly.

Can I gate repo-wide .NET retargeting across apps, unit tests, and packaging simultaneously?

Yes, you can gate repo-wide .NET retargeting across apps, unit tests, and packaging by enumerating every netX TFM and applying exact replacements to keep the entire solution consistent.

Why do .NET target framework changes cause test and packaging failures?

.NET target framework changes cause test and packaging failures when hidden TFM dependencies are missed during enumeration and hardcoded TFM references in tests or docs are not updated accordingly.

What is the best way to verify a .NET retargeting solution baseline?

The best way to verify a .NET retargeting baseline is to re-run the solution baseline checks after updating references, ensuring all packaging and test suites pass before completing the retargeting.