skills.rest
CoolCoderSuper
CoolCoderSuperCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

vmr-codeflow-status

Analyze VMR codeflow PR status for dotnet repositories using GitHub CLI and build freshness signals.

4|1|Updated May 1, 2026
Search Tags:#github#maestro#pr-status#vmr#codeflow#backflow#forward-flow
One-click install
npx skills add https://github.com/CoolCoderSuper/vb-ls --skill vmr-codeflow-status-coolcodersuper
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vmr-codeflow-status
Source: https://github.com/CoolCoderSuper/vb-ls/tree/main/roslyn/.github/skills/vmr-codeflow-status
Command: npx skills add https://github.com/CoolCoderSuper/vb-ls --skill vmr-codeflow-status-coolcodersuper

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Analyze VMR codeflow PR status for dotnet repositories to identify backflow and forward-flow health gaps and surface actionable remediation steps.

Core Features & Use Cases

  • PR health evaluation for backflow and forward-flow PRs in the VMR.
  • Detection of staleness and merge-conflict warnings with recommended actions.
  • Traceability of specific fixes through the VMR pipeline and cross-checks against official build freshness.
  • Consolidated summary to guide Maestro remediation decisions.

Quick Start

Run the Get-CodeflowStatus.ps1 script with a PR number and repository to generate a full codeflow health report.

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 VMR codeflow PR status for dotnet repositories?▼

To check VMR codeflow PR status, run the Get-CodeflowStatus.ps1 script with a PR number and repository name to generate a full health report identifying backflow and forward-flow bottlenecks.

Why does my Maestro subscription have a missing backflow PR?▼

A missing backflow PR in your Maestro subscription indicates pipeline health gaps. Diagnose the exact staleness or blockage by analyzing PR metadata and aka.ms build freshness signals to surface remediation guidance.

How do I trace a specific fix through the VMR pipeline?▼

You can trace a specific fix through the VMR pipeline by evaluating PR metadata and cross-checking official build freshness signals to verify whether your changes have successfully flowed through the codeflow pipeline.

Does the VMR codeflow status script require the GitHub CLI?▼

Yes, diagnosing VMR codeflow PR health requires the GitHub CLI installed and authenticated, as the script relies on it to fetch PR metadata and evaluate Maestro subscription build freshness signals.

What is the best way to diagnose stale codeflow PRs in dotnet?▼

The best way to diagnose stale codeflow PRs in dotnet is to analyze PR metadata against aka.ms build freshness signals to detect staleness and merge-conflict warnings, providing actionable remediation steps for Maestro subscriptions.

Related Skills

Explore More Software Engineering Skills→
dotnetdotnet
18.2k

vmr-codeflow-status

Analyze VMR codeflow PR status across dotnet repositories for freshness and flow health.

Official
Advanced
dotnetdotnet
13

flow-analysis

Analyze VMR codeflow to identify blocked, stale, or missing backflow PRs.

Official
Advanced
dotnetdotnet
13

flow-tracing

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

Official
Advanced
ilonatommyilonatommy
3

vmr-codeflow-status

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

Community
Advanced