code-review

Review dotnet/roslyn code changes for correctness, performance, and conventions.

4|1|Updated May 1, 2026
One-click install
npx skills add https://github.com/CoolCoderSuper/vb-ls --skill code-review-coolcodersuper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/CoolCoderSuper/vb-ls/tree/main/roslyn/.github/skills/code-review
Command: npx skills add https://github.com/CoolCoderSuper/vb-ls --skill code-review-coolcodersuper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review code changes against Roslyn conventions to ensure correctness, maintainability, and alignment with project standards before merging.

Core Features & Use Cases

  • Enforces Roslyn-style review practices across C# and VB code.
  • Guides reviewers to verify correctness, performance, style, and consistency with Roslyn patterns.
  • Helps teams maintain high-quality contributions in dotnet/roslyn.

Quick Start

Follow the reviewer checklist and apply the Roslyn-centric review mindset to every PR.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review a PR in dotnet/roslyn for correctness and performance?

To review a PR in dotnet/roslyn, you verify correctness, performance, and adherence to project conventions by critically analyzing context, edge cases, and potential regressions before merging.

What is the Roslyn code review process for C# and VB changes?

The Roslyn code review process enforces Roslyn-style review practices across C# and VB code by guiding reviewers through a checklist to verify style, consistency, and alignment with established patterns.

Does this code review skill work with both C# and VB code?

Yes, this code review skill enforces Roslyn-style review practices across both C# and VB code to help teams maintain high-quality contributions in the dotnet/roslyn repository.

Can I use this to check for regressions before merging code changes?

Yes, you can use this to check for regressions before merging code changes, as it requires critical analysis of context, edge cases, and potential regressions to ensure correctness and maintainability.

What's the best way to maintain code quality in dotnet/roslyn contributions?

The best way to maintain code quality in dotnet/roslyn contributions is to follow the reviewer checklist and apply a Roslyn-centric review mindset to every PR to ensure alignment with project standards.

Why should I use Roslyn conventions when reviewing pull requests?

You should use Roslyn conventions when reviewing pull requests to ensure correctness, maintainability, and alignment with established project standards before merging code changes into dotnet/roslyn.