skills.rest
lewing
lewingCOMMUNITY
Explore all skills by this author →
𝕏@lewingGitHub

flow-analysis

Diagnose VMR codeflow health by aggregating backflow PR status, forward flow blocks, and Maestro subscription signals.

4|1|Updated Feb 19, 2026
Search Tags:#subscription#ci#pr-analysis#maestro#vmr#codeflow#backflow
One-click install
npx skills add https://github.com/lewing/agent-plugins --skill flow-analysis-lewing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flow-analysis
Source: https://github.com/lewing/agent-plugins/tree/main/plugins/dotnet-dnceng/skills/flow-analysis
Command: npx skills add https://github.com/lewing/agent-plugins --skill flow-analysis-lewing

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps engineering teams quickly assess the health of VMR codeflow, determine why backflow PRs are stale or missing, and surface subscription/CI issues before they become blockers.

Core Features & Use Cases

  • Analyze backflow PR health, including staleness and conflicts
  • Inspect forward flow status and Maestro subscription health across repos
  • Quick triage for multi-repo flow health (e.g., dotnet/sdk, dotnet/runtime)

Quick Start

Run Get-CodeflowStatus.ps1 to analyze a repository's codeflow health or check for missing backflow PRs.

Frequently Asked Questions about flow-analysis

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

FAQPage Schema
How do I diagnose stale or missing VMR backflow PRs?▼

Diagnose VMR codeflow health by aggregating backflow PR status, forward flow blocks, and Maestro subscription signals to determine why codeflow PRs are stale or missing. Run Get-CodeflowStatus.ps1 to return a structured health snapshot.

Why does my VMR codeflow PR have a CI block?▼

VMR codeflow PR CI blocks occur when Maestro subscription health degrades or forward flow conflicts arise. Analyze the subscription signals and PR state across repositories to surface the specific CI or subscription issue blocking the flow.

How do I check Maestro subscription health across multiple dotnet repositories?▼

Check Maestro subscription health across multiple dotnet repositories by running a multi-repo codeflow analysis to inspect forward flow status and aggregate subscription signals, returning a structured health snapshot for repos like dotnet/sdk and dotnet/runtime.

Do I need Maestro MCP data and GitHub access to analyze VMR codeflow?▼

Yes, analyzing VMR codeflow requires access to Maestro MCP data and GitHub PR state information. These dependencies provide the necessary subscription signals and pull request statuses to enforce safe analysis pipelines and generate the health snapshot.

What's the best way to triage codeflow blocks for dotnet/runtime and dotnet/sdk?▼

The best way to triage codeflow blocks for dotnet/runtime and dotnet/sdk is to run a multi-repo flow health analysis that aggregates Maestro subscription signals and backflow PR staleness, surfacing CI conflicts and missing PRs in a structured snapshot.

Related Skills

Explore More Software Engineering Skills→
duggal1duggal1
2

mcporter

Manage MCP servers via mcporter CLI over HTTP or stdio.

Community
Intermediate
CoolCoderSuperCoolCoderSuper
4

vmr-codeflow-status

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

Community
Advanced
ilonatommyilonatommy
3

vmr-codeflow-status

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

Community
Advanced
mostafa-ismail-2004mostafa-ismail-2004

github-ops

Manage GitHub repository operations via the gh CLI.

Community
Advanced