flow-tracing

Trace dependency changes through the .NET VMR pipeline using manifests.

13|20|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/dotnet/arcade-skills --skill flow-tracing-dotnet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flow-tracing
Source: https://github.com/dotnet/arcade-skills/tree/main/plugins/dotnet-dnceng/skills/flow-tracing
Command: npx skills add https://github.com/dotnet/arcade-skills --skill flow-tracing-dotnet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, az, git, and includes scripts (resource) and references (resource) components.

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.

Frequently Asked Questions about flow-tracing

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

FAQPage Schema
How do I trace a dependency change across .NET repositories?

To trace a dependency change across .NET repositories, resolve the source commit and follow manifests through the VMR pipeline. This Skill confirms propagation by reading source-manifest.json and Version.Details.xml using Maestro tooling.

How can I find the runtime SHA present in a specific .NET SDK build?

Find the runtime SHA in a .NET SDK build by decoding the SDK version string to identify the corresponding VMR branch. Use the Get-SdkVersionTrace.ps1 script to resolve component SHAs via source-manifest.json or Version.Details.xml.

How does dependency flow tracing work through the .NET VMR pipeline?

Dependency flow tracing works by resolving a source commit and following manifests to confirm propagation across .NET repos. It leverages Maestro and GitHub MCP tooling, plus az CLI and gh api, to map changes through servicing topology branches.

Can I trace SDK versions to VMR commits using GitHub CLI and az CLI?

Yes, you can trace SDK versions to VMR commits using GitHub CLI and az CLI. The Skill leverages gh api and az CLI alongside Maestro MCP tooling to map SDK version strings to their corresponding VMR branch and component SHAs.

What's the best way to determine if a change from one .NET repo has reached another?

The best way to determine if a change from one .NET repo has reached another is cross-repo flow tracing. Read the source-manifest.json and use Maestro/MCP tooling to follow dependency chains across 1xx/2xx/3xx servicing branches.

Do I need PowerShell to run SDK version traces for .NET servicing branches?

Yes, you need PowerShell to run the Get-SdkVersionTrace.ps1 script for SDK version traces. Run this script from the scripts folder with a valid SDK version to resolve VMR branches and component SHAs across servicing topology branches.