code-review

Identify and report quality issues in C# code during code reviews.

Updated Aug 23, 2026

Search Tags:#testing #csharp #architecture #quality #dotnet #code-review

Ready to run

npx skills add https://github.com/kirillshilin/instructions --skill code-review-kirillshilin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/kirillshilin/instructions/tree/main/obsolete/claude/skills/code-review
Command: npx skills add https://github.com/kirillshilin/instructions --skill code-review-kirillshilin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, repeatable process for reviewing C# code to improve architecture, correctness, async usage, error handling, naming, and test coverage during pull requests or file reviews.

Core Features & Use Cases

Architecture checks ensure dependencies and module boundaries are respected.
Quality checks cover correctness, async patterns, error handling, and naming conventions.
Test visibility verifies presence of tests for new or changed code and highlights gaps in coverage.

Quick Start

Review the changed C# files in the PR and provide a structured assessment of architecture, correctness, async usage, error handling, naming, and test coverage.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I review C# code for quality issues in a pull request?▼

The code review checks C# dependencies and module boundaries to ensure architecture is respected. It verifies proper dependencies and consistent module separation across .NET projects.

How do I check async patterns and error handling in .NET code reviews?▼

Test visibility during code review verifies the presence of tests for new or changed C# code and highlights gaps in test coverage. It checks whether changed .NET files have corresponding tests.

Can I use automated code review for .NET projects to enforce naming conventions?▼

This code review process targets C# files in .NET projects, checking architecture, async patterns, error handling, naming, and test coverage. It applies to pull requests and changed files without requiring external dependencies.

What's the best way to identify architecture and dependency issues in C# code?▼

The best way to identify architecture and dependency issues in C# code is to apply architecture checks during pull request reviews, ensuring proper dependencies and module boundaries are respected in .NET projects.