code-review

Review .NET/C# pull requests or staged diffs and classify issues by severity.

2|Updated May 2, 2026
One-click install
npx skills add https://github.com/andrecini/dotnet-squad-copilot-agent --skill code-review-andrecini
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/andrecini/dotnet-squad-copilot-agent/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/andrecini/dotnet-squad-copilot-agent --skill code-review-andrecini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you review Pull Requests or staged changes quickly and consistently, identifying architectural, code quality, validation, security, and documentation issues before they reach the pipeline.

Core Features & Use Cases

  • PR or staging diff intake: Reviews all files changed in a specified Pull Request link or the current staged changes in Git.
  • Checklist-driven, category-based analysis: Applies only the relevant checklist categories inferred from the touched layers and artifact types.
  • Actionable findings with severity: Classifies issues as 🔴 Blocker, 🟡 Warning, or 🔵 Suggestion and includes “how it is” plus “how it should be” guidance with code examples.
  • Single-chat report only: Produces a structured report in the chat without modifying code, commenting on PRs, or approving automatically.

Quick Start

Ask the agent: “Review this Pull Request: <PR link> and generate the structured code review report with blockers, warnings, and suggestions.”

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 pull request for architectural and security issues in .NET?

Reviewing a pull request for architectural and security issues in .NET requires analyzing staged diffs across Presentation, Application, Domain, and Infrastructure layers. This Skill performs a read-only analysis to produce a structured report with actionable remediation guidance and severity classifications.

Can I generate a structured code review report for staged changes without modifying my codebase?

Yes, you can generate a structured code review report for staged changes without modifying your codebase. This Skill enforces read-only analysis guardrails, ensuring it only outputs a severity-classified report in the chat without writing code, commenting on PRs, or automatically approving changes.

Does this code review tool support Minimal APIs and dependency injection validation?

This code review tool supports Minimal APIs and dependency injection validation. It applies a checklist-driven analysis to .NET/C# changes, verifying validators, DI configurations, logging, and unit tests while only evaluating the relevant artifact types inferred from the touched layers.

What is the best way to classify code quality findings when reviewing a PR diff?

The best way to classify code quality findings when reviewing a PR diff is by using a tiered severity system. This Skill categorizes issues as Blockers, Warnings, or Suggestions, providing specific examples of the current state versus the recommended fix for each finding.

How do I ensure my C# unit tests meet quality standards before merging a pull request?

To ensure C# unit tests meet quality standards before merging, analyze the staged diffs using a checklist-driven review. This Skill evaluates the Tests layer of your .NET changes, identifying validation and documentation issues and outputting them in a structured report.

When should I use an automated code review report instead of manually checking my staged Git diff?

You should use an automated code review report when you need consistent, category-based analysis of a staged Git diff. It is ideal for quickly identifying architectural flaws, security vulnerabilities, and documentation gaps across .NET layers before they reach your pipeline.