flow-tracing

What problem does it solve?

Trace dependency flow across .NET repos through the VMR pipeline. USE FOR: checking if a PR/commit from repo A has reached repo B, finding what runtime SHA is in an SDK build, tracing dependency versions through the VMR, checking if a commit is included in an SDK build, decoding SDK version strings, "has my fix reached runtime", "did roslyn#80873 flow to runtime", "what SHA is in SDK version X", cross-repo dependency tracing, mapping SDK versions to VMR commits. DO NOT USE FOR: codeflow PR health or staleness (use flow-analysis skill), CI build failures (use ci-analysis skill). INVOKES: maestro and GitHub MCP tools, Get-SdkVersionTrace.ps1 script.

Core Features & Use Cases

• Cross-Repo Flow Trace: Determine whether a change from repo A has reached repo B by inspecting source-manifest.json on the VMR and checking Version.Details.xml for servicing branches.
• SDK Version Trace: Decode an SDK version, map to the VMR branch, locate the unified build, and walk the dependency chain via source-manifest.json and Version.Details.xml.
• Operational Guidance: Invoke the Get-SdkVersionTrace.ps1 script to perform end-to-end tracing across the VMR.

Quick Start

Run the flow-tracing skill against a PR to verify whether the change propagated through the VMR to downstream repos.