Common-VS2019/.agents/skills/common-dotnet-change/SKILL.md

name, description

name	description
common-dotnet-change	Coordinate compatibility and validation for Common-VS library changes affecting BusinessMgr, Sandtrap, or Sandalwood consumers; not a general .NET workflow.

Common .NET Change

Use this workflow only for changes to Common-VS libraries whose compatibility or validation crosses into BusinessMgr, Sandtrap, or Sandalwood. It is not a general .NET build, package, or project-change workflow. It supplements, and does not replace, the relevant repositories' AGENTS.md files.

1. Read Common's AGENTS.md, docs/topics.md, and docs/component-reviews.md. Read the corresponding consumer guidance and trackers when a consumer is in scope.
2. Check the Git status of every affected repository before editing. Treat each repository as an independent change set and preserve unrelated work.
3. Identify the changed public surface, direct project references, target frameworks, package ownership, and in-scope consumers. Preserve relative workspace layout and public compatibility unless the task explicitly authorizes a breaking change.
4. For framework upgrades, coordinate dependency order across Common and consumers. Where an atomic move is impractical, prefer a temporary compatible target when practical, migrate consumers, then remove the old target only after no in-scope consumer needs it.
5. Build and test the directly affected Common project first. Then validate each affected consumer using its repository's standard validation entry point (eng/validate.ps1 where available). Respect platform, workload, database, and Visual Studio tooling requirements; report unavailable validation separately from source failures.
6. If validation requirements or their scope changed, update the owning eng/validate.ps1 and eng/README.md, then run the updated validation.
7. Update the relevant topic and component trackers with concrete changes and validation evidence. Do not claim broader consumer compatibility than the checks establish.