code-review-workflow

Generate severity-ranked code review findings for .NET pull requests using Roslyn MCP analysis.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/Maj3D10/Training-Platform --skill code-review-workflow-maj3d10
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-workflow
Source: https://github.com/Maj3D10/Training-Platform/tree/main/.agent/skills/code-review-workflow
Command: npx skills add https://github.com/Maj3D10/Training-Platform --skill code-review-workflow-maj3d10

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams perform consistent, high-signal code reviews for .NET changes by guiding an AI through MCP-based analysis first and then structured human-style verification.

Core Features & Use Cases

  • MCP-first .NET PR analysis: Runs Roslyn MCP tools to detect antipatterns, compiler diagnostics, public API changes, references, architecture issues, and test coverage gaps.
  • Structured severity output: Produces findings split into Critical (must fix), Warning (should fix), and Suggestions (nice to have), plus a dedicated Architecture Compliance and What's Good section.
  • Review modes by change size: Uses a full workflow for larger PRs and a quick workflow for small changes, with an architecture-only option when relevant.

Quick Start

Ask the AI to run a code review for your pull request by saying: "Review PR changes using the code-review-workflow skill and prioritize critical and security findings first."

Frequently Asked Questions about code-review-workflow

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

FAQPage Schema
How do I perform an automated code review for .NET pull requests?

Automated .NET code review combines Roslyn MCP analysis with targeted manual inspection to evaluate C# pull requests. It generates structured findings ranked by severity to satisfy correctness, security, performance, and architecture compliance checks.

What is the best way to check architecture compliance and test coverage in C# changes?

The best way to check architecture compliance and test coverage in C# changes is running Roslyn MCP analysis. It detects module boundary violations, reference issues, and coverage gaps, producing a dedicated compliance section in the review output.

Can I use Roslyn analysis for security and blast-radius assessment in refactors?

Yes, Roslyn analysis supports security and blast-radius assessment during refactors by evaluating public API changes and tracking references across modified C# files to determine the potential impact of updates.

How does the code review workflow handle different PR sizes?

The code review workflow handles different PR sizes by applying a full workflow for larger pull requests and a quick workflow for small changes. It also offers an architecture-only review mode for targeted module updates.

Do I need specific tools to get severity-ranked code review findings for my pull request?

Yes, you need Roslyn MCP tools to generate severity-ranked code review findings. The workflow relies on these tools to detect compiler diagnostics and antipatterns before structuring the output into Critical, Warning, and Suggestion categories.