Trace dependency flow across .NET repos through the VMR pipeline.
npx skills add https://github.com/lewing/agent-plugins --skill flow-tracing
Please help me install this Agent Skill. Skill: flow-tracing Source: https://github.com/lewing/agent-plugins/tree/main/plugins/dotnet-dnceng/skills/flow-tracing Command: npx skills add https://github.com/lewing/agent-plugins --skill flow-tracing
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.
Run the flow-tracing skill against a PR to verify whether the change propagated through the VMR to downstream repos.
High-intent search queries and answers about installing and using this skill.
To trace cross-repo dependency flow, run the skill against a PR to resolve SHAs via source-manifest.json and Version.Details.xml, verifying propagation through the VMR pipeline to downstream repositories.
Decode the SDK version string, map it to the VMR branch, locate the unified build, and walk the dependency chain via source-manifest.json to find the runtime SHA included in that specific SDK version.
Yes, the skill checks Version.Details.xml to resolve SHAs and trace dependency versions for servicing branches, while 1xx full builds rely on resolving source-manifest.json on the VMR.
Yes, mapping SDK builds back to contributing commits requires access to Maestro MCP tooling and the Get-SdkVersionTrace.ps1 script to perform end-to-end tracing across the VMR.
Avoid using this skill for codeflow PR health or staleness checks, or for diagnosing CI build failures; use flow-analysis or ci-analysis skills instead for those specific scenarios.
Invoke the Get-SdkVersionTrace.ps1 script to decode the SDK version, map it to the VMR branch, locate the unified build, and walk the dependency chain via source-manifest.json to trace it to a VMR commit.
dotnetTrace dependency changes through the .NET VMR pipeline using manifests.
JoeyJoziahCoordinate cross-repository changes and synchronization across GitHub repositories.
lewingDiagnose VMR codeflow health by aggregating backflow PR status, forward flow blocks, and Maestro subscription signals.
ilonatommyAnalyze VMR codeflow PR status for .NET repositories using GitHub CLI and darc.
