// Analyze VMR codeflow PR status for dotnet repositories. Use when investigating stale codeflow PRs, checking if fixes have flowed through the VMR pipeline, debugging dependency update issues in PRs authored by dotnet-maestro[bot], checking overall flow status for a repo, or diagnosing why backflow PRs are missing or blocked.
Review code changes in dotnet/runtime for correctness, performance, and consistency with project conventions. Use when reviewing PRs or code changes.
Analyze CI build and test status from Azure DevOps and Helix for dotnet repository PRs. Use when checking CI status, investigating failures, determining if a PR is ready to merge, or given URLs containing dev.azure.com or helix.dot.net. Also use when asked "why is CI red", "test failures", "retry CI", "rerun tests", or "is CI green".
Extract a standalone JIT regression test case from a given GitHub issue and save it under the JitBlue folder. Use this when asked to create or extract a JIT regression test from an issue.
Generate and run ad hoc performance benchmarks to validate code changes. Use this when asked to benchmark, profile, or validate the performance impact of a code change in dotnet/runtime.
| name | vmr-codeflow-status |
| description | Analyze VMR codeflow PR status for dotnet repositories. Use when investigating stale codeflow PRs, checking if fixes have flowed through the VMR pipeline, debugging dependency update issues in PRs authored by dotnet-maestro[bot], checking overall flow status for a repo, or diagnosing why backflow PRs are missing or blocked. |
Analyze the health of VMR codeflow PRs in both directions:
dotnet/dotnet → product repos (e.g., dotnet/sdk)dotnet/dotnet🚨 NEVER use
gh pr review --approveor--request-changes. Only--commentis allowed. Approval and blocking are human-only actions.
gh) — must be installed and authenticated (gh auth login)Use this skill when:
dotnet-maestro[bot]) has failing tests and you need to know if it's stale| Mode | Use When | Required Params |
|---|---|---|
| PR analysis | Investigating a specific codeflow PR | -PRNumber (and optionally -Repository) |
Flow health (-CheckMissing) | Checking overall repo flow status | -CheckMissing (optional: -Repository, -Branch) |
⚠️ Common mistake: Don't use
-PRNumberand-CheckMissingtogether — they are separate modes.-CheckMissingscans branches discovered from open and recent backflow PRs (unless-Branchis provided), not a specific PR.
# Check codeflow PR status (most common)
./scripts/Get-CodeflowStatus.ps1 -PRNumber 52727 -Repository "dotnet/sdk"
# Trace a specific fix through the pipeline
./scripts/Get-CodeflowStatus.ps1 -PRNumber 52727 -Repository "dotnet/sdk" -TraceFix "dotnet/runtime#123974"
# Show individual VMR commits that are missing
./scripts/Get-CodeflowStatus.ps1 -PRNumber 52727 -Repository "dotnet/sdk" -ShowCommits
# Check overall flow health for a repo (backflow + forward flow)
./scripts/Get-CodeflowStatus.ps1 -Repository "dotnet/roslyn" -CheckMissing
# Check a specific branch only
./scripts/Get-CodeflowStatus.ps1 -Repository "dotnet/sdk" -CheckMissing -Branch "main"
| Parameter | Required | Default | Description |
|---|---|---|---|
-PRNumber | Yes (unless -CheckMissing) | — | GitHub PR number to analyze |
-Repository | No | dotnet/sdk | Target repo in owner/repo format |
-TraceFix | No | — | Trace a repo PR through the pipeline. Format: owner/repo#number (e.g., dotnet/runtime#123974) |
-ShowCommits | No | $false | Show individual VMR commits between PR snapshot and branch HEAD |
-CheckMissing | No | $false | Check overall flow health: missing backflow PRs, forward flow status, and official build freshness |
-Branch | No | — | With -CheckMissing, only check a specific branch (e.g., main, release/10.0) |
-TraceFix) — Checks if a specific fix has flowed through VMR → codeflow PR-CheckMissing)aka.ms shortlinks for latest published VMR build dates per channeldotnet/dotnet for staleness and conflicts❌ Never assume "Unknown" health means healthy. When
ghAPI calls fail (auth, rate limiting), the script returns "Unknown" status — this is explicitly excluded from healthy/covered counts.
⚠️ aka.ms redirect behavior: 301 is expected and treated as a valid product URL (→ ci.dot.net). Non-301 redirects (often 302, which goes to Bing) indicate an invalid URL. The script only accepts 301.
darc vmr resolve-conflict command.Manual commits on the PR branch are at risk if the PR is closed or force-triggered. The script lists them so you can decide whether to preserve them.
When using -TraceFix:
After analyzing the codeflow status, common next steps involve darc commands:
# Force trigger the subscription to get a fresh codeflow update
darc trigger-subscriptions --id <subscription-id> --force
# Normal trigger (only works if not stale)
darc trigger-subscriptions --id <subscription-id>
# Check subscription details
darc get-subscriptions --target-repo dotnet/sdk --source-repo dotnet/dotnet
# Get BAR build details
darc get-build --id <bar-build-id>
# Resolve codeflow conflicts locally
darc vmr resolve-conflict --subscription <subscription-id>
Install darc via eng\common\darc-init.ps1 in any arcade-enabled repository.