flow-analysis

Diagnosing VMR codeflow health involves analyzing backflow PRs to identify blocked, stale, or missing pull requests across dotnet repositories. The analysis generates a structured health report with actionable remediation guidance.

VMR codeflow health analysis surfaces blocked, stale, or missing backflow PRs across code repositories. You need it when tracking per-repo or multi-repo flow health, including single-PR analysis, repo-wide health checks, and forward-flow investigations.

Yes, you can check codeflow status across multiple dotnet repositories at scale. The analysis supports per-repo and multi-repo flow health scenarios, applying script-driven data collection and Maestro MCP enrichment for comprehensive coverage.

Yes, the analysis integrates with Maestro MCP to retrieve subscription and build freshness data. This enrichment is combined with script-driven data collection to provide a complete picture of VMR codeflow health and identify missing backflow PRs.

You can trigger or force-trigger Maestro subscriptions during codeflow analysis using optional action parameters. This allows you to initiate backflow PRs directly while investigating forward-flow blockers and recovery paths across dotnet repositories.

The best way to investigate forward-flow blockers is running an end-to-end codeflow analysis workflow. It identifies blockers and recovery paths across dotnet repositories by combining script-driven data collection with Maestro subscription freshness data.