code-review-dotnet

Automate pre-merge C#/.NET code review for production-critical bugs and security risks.

12|2|Updated May 4, 2020
One-click install
npx skills add https://github.com/hoangnh2412/jarvis --skill code-review-dotnet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-dotnet
Source: https://github.com/hoangnh2412/jarvis/tree/main/.opencode/skills/code-review-dotnet
Command: npx skills add https://github.com/hoangnh2412/jarvis --skill code-review-dotnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual code reviews for C#/.NET pull requests often miss high-severity production risks like security vulnerabilities, data corruption, and concurrency bugs, while wasting time on low-impact style nitpicks. This Skill automates the initial review pass to catch critical issues early, reducing the burden on human reviewers and preventing costly production incidents.

Core Features & Use Cases

  • Comprehensive C#/.NET Checklist: Covers async/await correctness, EF Core query issues, DI lifetime mismatches, nullable reference safety, and common security vulnerabilities.
  • Jarvis Framework Support: Includes specialized checks for solutions built with the Jarvis clean architecture, including multitenancy rules, OpenTelemetry configuration, and layer dependency validation.
  • Use Cases: Review code before opening a PR, validate feature/fix implementations for production readiness, and get a second opinion on complex .NET patterns like async streams, transaction boundaries, and caching logic.

Quick Start

Use the code-review-dotnet skill to review all changes in your current PR against the main branch and get a prioritized list of production risks and suggested fixes.

Frequently Asked Questions about code-review-dotnet

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

FAQPage Schema
How do I automate C# code review to catch production risks before opening a PR?

Automate C# code review by applying a checklist for async patterns, EF Core usage, and DI lifetime mismatches to catch production-critical bugs pre-merge. This process prioritizes high-impact fixes over minor style nitpicks, reducing manual review burden.

What common EF Core and async concurrency bugs should a .NET pull request review target?

A .NET pull request review should target EF Core query issues, async/await correctness, and DI lifetime mismatches. Identifying these concurrency and data corruption risks early prevents costly production incidents and ensures backend stability.

Does automated .NET code review work with the Jarvis clean architecture framework?

Yes, automated .NET code review works with the Jarvis clean architecture framework. It includes specialized checks for multitenancy rules, OpenTelemetry configuration, and layer dependency validation to ensure framework-specific production readiness.

What's the best way to validate multitenancy and dependency injection configurations in C#?

The best way to validate multitenancy and dependency injection configurations in C# is using an automated review pass. It checks DI lifetime mismatches and multitenancy rules against your architecture, delivering prioritized execution paths for any flagged problems.

How are identified issues prioritized during an automated .NET code review?

During an automated .NET code review, identified issues are prioritized into critical issues, suggestions, and best practices. This categorization provides explicit execution paths for all flagged problems, allowing developers to focus immediately on high-impact fixes.