vmr-codeflow-status

Analyze VMR codeflow PR status for .NET repositories using GitHub CLI and darc.

3|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/ilonatommy/copilot-skills --skill vmr-codeflow-status-ilonatommy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vmr-codeflow-status
Source: https://github.com/ilonatommy/copilot-skills/tree/main/runtime-skills/vmr-codeflow-status
Command: npx skills add https://github.com/ilonatommy/copilot-skills --skill vmr-codeflow-status-ilonatommy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps diagnose and understand the status of codeflow Pull Requests (PRs) within the .NET VMR (Versioned Repository) ecosystem, ensuring smooth integration of code changes across repositories.

Core Features & Use Cases

  • PR Status Analysis: Quickly assess if a codeflow PR is up-to-date, stale, or in conflict.
  • Missing PR Detection: Identify if expected backflow PRs are missing for a repository.
  • Forward Flow Monitoring: Check the status of PRs flowing from product repositories back into the VMR.
  • Use Case: When a .NET product repository's PR is failing or delayed, use this Skill to determine if the issue stems from VMR codeflow, staleness, or conflicts, and get actionable insights.

Quick Start

Analyze the status of codeflow PR number 52727 in the dotnet/sdk repository.

Frequently Asked Questions about vmr-codeflow-status

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

FAQPage Schema
How do I check the status of a VMR codeflow PR in a .NET repository?

To check VMR codeflow PR status, analyze the pull request to identify staleness, conflicts, and missing backflow PRs using GitHub CLI and darc commands, yielding actionable remediation insights for .NET repositories.

Why is my .NET product repository PR failing or delayed in the VMR codeflow?

A .NET product repository PR fails or delays in VMR codeflow due to staleness, conflicts, or missing backflow PRs; analyzing PR health and VMR build freshness isolates the root cause and provides remediation steps.

How do I detect missing backflow PRs for a .NET VMR repository?

Detect missing backflow PRs for a .NET VMR repository by executing diagnostic darc commands and GitHub CLI checks to monitor forward flow status and identify absent expected pull requests.

Can I use GitHub CLI and darc commands to diagnose VMR build freshness?

Yes, you can use GitHub CLI and darc commands to diagnose VMR build freshness, evaluating forward flow status and PR health to determine if codeflow integration is up-to-date or requires remediation.

What is the best way to analyze forward flow status from product repos back into the VMR?

The best way to analyze forward flow status from product repos back into the VMR is running diagnostics via darc commands and GitHub CLI to assess PR health and identify stale or conflicting codeflows.