code-review-workflow

A structured .NET code review uses Roslyn MCP analysis on changed C# files to detect antipatterns, extract public APIs, map reference blast radius, and generate severity-ranked findings. It validates architecture boundaries and test coverage before manual code reading.

Reference blast radius mapping identifies how far changes in C# files propagate across the project graph. It assesses risk by extracting public APIs and tracing references, helping prioritize review focus on changes with wider architectural impact.

Roslyn MCP runs automated analysis on changed C# files to detect antipatterns and compiler diagnostics before manual review. This MCP-first execution flow ensures correctness and security issues are caught programmatically, producing structured severity-ranked feedback.

Yes, architecture compliance is checked by validating project dependency direction and enforcing module boundary rules within the project graph. This ensures changed files respect architectural constraints and identifies violations before merging.

Yes, test coverage validation maps changed logic to existing tests to identify missing coverage. It runs after Roslyn MCP diagnostics and architecture checks, ensuring modified C# files have corresponding test validation before producing final severity-ranked findings.

Use a severity-based review workflow that runs MCP diagnostics, assesses blast radius across all changed files, checks architecture boundaries, and reports missing test coverage. This produces risk-ranked, actionable feedback separating Critical, Warnings, and Suggestions.