code-review

Reviews ERP code against SQL, C#, and TypeScript conventions with blocker detection.

Updated Aug 18, 2026
One-click install
npx skills add https://github.com/Aurelian1974/ERPEnterprise --skill code-review-aurelian1974
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/Aurelian1974/ERPEnterprise/tree/main/.github/skills/code-review
Command: npx skills add https://github.com/Aurelian1974/ERPEnterprise --skill code-review-aurelian1974

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Enforcing consistent coding standards across a multi-module ERP codebase is hard to do manually, and critical violations like inline SQL, exposed connection strings, or missing tenant filters often slip through reviews. ## Core Features & Use Cases - Blocker Detection: Instantly flags hard rejections such as inline SQL in C#, committed connection strings, EF Core usage, cross-module references, and NEWID() on primary keys. - Layered Checklists: Provides structured review checklists for SQL objects and naming, multi-tenancy rules, C# architecture (VSA, Result<T>, repositories), and TypeScript/React patterns (TanStack Query, Zod, strict typing). - Use Case: When a developer opens a pull request adding a new invoice feature, run this review to verify the stored procedures use CREATE OR ALTER, every query filters by tenant_id, handlers return Result<T>, and the frontend avoids barrel files and any types. ## Quick Start Review this pull request and check whether the code follows the project's SQL, C#, and frontend conventions.

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 against project coding conventions?▼

Run a structured code review that checks each layer against defined checklists: SQL naming and multi-tenancy rules, C# architecture and Result<T> patterns, and TypeScript data fetching standards. Blocker violations like inline SQL or exposed connection strings are rejected immediately.

What are common code review blockers in C# ERP projects?▼

Typical blockers include inline SQL strings in C# code, connection strings committed to appsettings.json, EF Core usage where stored procedures are required, direct references between modules, and NEWID() defaults on primary key columns.

How do I enforce multi-tenancy in SQL stored procedures?▼

Every table must include a tenant_id UNIQUEIDENTIFIER NOT NULL column, every query must filter with AND tenant_id = @TenantId, and tenant_id must be the first column in any composite index. Reviews verify all three rules on every new object.

Does this review cover TypeScript and React frontend code?▼

Yes, the checklist covers TanStack Query for server data, React Hook Form with Zod schemas, strict TypeScript with no any types, no barrel files, and secure JWT storage outside localStorage.

Why use Result<T> instead of throwing exceptions in handlers?▼

Result<T> makes business errors explicit in the return type instead of relying on exceptions for control flow. Errors are defined in a static {Module}Errors class, and controllers check result.IsSuccess before building the response.