What problem does it solve?
Trace dependency flow across .NET repositories through the VMR pipeline. This Skill helps teams determine whether a change from one repository has propagated to another, identify the runtime SHA present in an SDK build, and map SDK versions to VMR commits. It supports both cross-repo flow tracing and SDK version tracing, and leverages source-manifest.json and Version.Details.xml as needed.
Core Features & Use Cases
- Cross-repo flow trace: determine if a change from repo A has reached repo B by reading the source-manifest.json and Maestro/MCP tooling.
- SDK version trace: decode an SDK version, identify the corresponding VMR branch, locate the build, and resolve the component SHA via source-manifest.json or Version.Details.xml.
- Servicing topology awareness: follow dependency chains across 1xx/2xx/3xx branches to map to the correct upstream SHAs.
Quick Start
Run the Get-SdkVersionTrace.ps1 script from the scripts folder with a valid SDK version to begin tracing.