code-review-workflow

Analyze changed C# files in .NET pull requests with Roslyn-based MCP tools.

1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/Trossitec/dotnet-claude-kit --skill code-review-workflow-trossitec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-workflow
Source: https://github.com/Trossitec/dotnet-claude-kit/tree/main/skills/code-review-workflow
Command: npx skills add https://github.com/Trossitec/dotnet-claude-kit --skill code-review-workflow-trossitec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves inconsistent, incomplete, and hard-to-prioritize pull request reviews in .NET projects by providing a repeatable, MCP-first workflow that checks correctness, security, performance, architecture compliance, and test coverage.

Core Features & Use Cases

  • MCP-first analysis: Runs Roslyn MCP tools (e.g., detect antipatterns, compiler diagnostics, public API diffs) before manual file reading to focus review effort on what matters.
  • Severity-based findings: Produces actionable findings categorized as Critical, Warning, or Suggestion to prevent important issues from being buried.
  • Full PR or Quick Review modes: Uses a full structured flow for larger PRs and a lightweight flow for small changes while maintaining consistent output structure.
  • Blast radius and architecture checks: Assesses impact via reference finding and validates dependency direction with project graph inspection.
  • Test coverage validation: Uses a test coverage map to flag missing tests for changed or newly introduced types.

Quick Start

Tell the AI to review your pull request by loading this skill when you say: "review PR", including the list of changed .cs files and the relevant scope (files, projects, or symbols) for analysis.

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 a structured code review for .NET pull requests?

Structured code review for .NET pull requests uses MCP-first Roslyn tooling to analyze changed C# files and public APIs. This workflow validates architecture compliance, checks test coverage, and produces severity-graded findings with actionable remediation steps.

How does Roslyn-backed MCP tooling analyze C# files?

Roslyn-backed MCP tooling analyzes C# files by running diagnostics, detecting antipatterns, and diffing public APIs before manual reading. It assesses blast radius via reference finding and validates dependency direction using project graph inspection.

Can I validate test coverage and architecture compliance during a PR review?

Yes, you can validate test coverage and architecture compliance during a PR review. The workflow uses a test coverage map to flag missing tests for changed types and inspects the project graph to enforce correct dependency direction.

What's the best way to prioritize issues found in C# code changes?

Prioritizing issues in C# code changes is best handled by generating severity-graded findings categorized as Critical, Warning, or Suggestion. This prevents important security and architecture issues from being buried in manual file review.

Does this code review workflow handle both small fixes and large feature PRs?

Yes, this code review workflow handles both small fixes and large feature PRs. It applies a full structured flow for larger PRs and a lightweight flow for small changes while maintaining a consistent output structure.

When do I need MCP tools to check public API surface changes?

You need MCP tools to check public API surface changes when assessing feature PRs, bug fixes, or module additions. The get_public_api tool extracts diffs to ensure stability and correctness across the .NET codebase.