vmr-codeflow-status

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

18.2k|5.5k|Updated Sep 24, 2019
One-click install
npx skills add https://github.com/dotnet/runtime --skill vmr-codeflow-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vmr-codeflow-status
Source: https://github.com/dotnet/runtime/tree/main/.github/skills/vmr-codeflow-status
Command: npx skills add https://github.com/dotnet/runtime --skill vmr-codeflow-status

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 stale PRs, verify fixes have flowed through the VMR, troubleshoot Maestro-driven updates, and assess overall flow health across repos.

Core Features & Use Cases

  • Health checks for codeflow PRs, including staleness and conflicts.
  • Tracing specific fixes through the pipeline to confirm they reached the codeflow PR.
  • End-to-end flow health assessment for backflow and forward flow across multiple repos.
  • Quick diagnostics of why backflow PRs might be missing or blocked.

Quick Start

Supply the repository and PR number to analyze a specific codeflow PR and view a concise health summary.

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 across dotnet repositories?

You can check VMR codeflow PR status by analyzing the PR metadata to determine freshness, identify staleness, and assess conflicts across dotnet repositories. It reports a structured health summary with actionable recommendations.

What is the best way to troubleshoot missing or blocked Maestro backflow PRs?

Troubleshooting Maestro backflow PRs involves assessing end-to-end flow health and verifying official build freshness across multiple branches. Quick diagnostics help identify why backflow PRs might be missing or blocked in the pipeline.

Can I trace a specific fix through the VMR codeflow pipeline?

Yes, you can trace specific fixes through the pipeline to confirm they reached the codeflow PR. This process verifies PR metadata in the body and assesses conflicts to ensure the fix has properly flowed through the VMR.

Does this codeflow analysis support both forward flow and backflow PRs?

VMR codeflow analysis applies to both backflow and forward-flow PRs. It evaluates staleness warnings and checks official build freshness across multiple branches to provide a comprehensive flow health assessment.

Why is my dotnet VMR codeflow PR showing as stale?

A dotnet VMR codeflow PR shows as stale when freshness checks identify it hasn't been recently updated or conflicts exist. The analysis verifies PR metadata and reports these issues in a structured health summary.

Do I need gh installed to analyze VMR codeflow PR health?

Yes, you need the gh command-line tool installed as a dependency to analyze VMR codeflow PR health. The Skill utilizes gh to verify PR metadata, assess conflicts, and generate health summaries across dotnet repositories.