database-review

Analyze .NET database migrations, models, and mappings for schema quality and dialect consistency.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/MudraMartin/dotlight-skillset --skill database-review-mudramartin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database-review
Source: https://github.com/MudraMartin/dotlight-skillset/tree/main/dotnet/database-review
Command: npx skills add https://github.com/MudraMartin/dotlight-skillset --skill database-review-mudramartin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies schema quality issues and dialect inconsistencies in .NET databases, preventing merge conflicts and ensuring database integrity.

Core Features & Use Cases

  • Schema Quality Gate: Flags issues like dialect deviations, test-shaped schema smells, and broken versioning mechanics.
  • Dialect Consistency: Checks for naming, key strategy, versioning patterns, audit columns, soft delete, and type dialect consistency.
  • Review Procedure: Provides a step-by-step guide to review schema changes and apply detection rules.
  • Output Format: Generates a clear report with findings, severity, and gate status for merge decisions.

Quick Start

Run the 'database-review' skill to check the schema consistency of your .NET database before merging changes.

Frequently Asked Questions about database-review

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

FAQPage Schema
How do I check .NET database schema consistency before merging migrations?

Checking database schema consistency involves analyzing migrations, models, and mappings to detect naming deviations, key strategy inconsistencies, and audit column discrepancies before merging database changes.

What are common schema quality issues in .NET database migrations?

Common schema quality issues in .NET databases include dialect deviations, test-shaped schema smells, broken versioning mechanics, soft delete inconsistencies, and naming deviations across different database mappings.

How do I detect a second dialect in my .NET database schema?

Detecting a second dialect requires analyzing your .NET database migrations and mappings to identify inconsistencies in naming conventions, key strategies, versioning patterns, and audit columns that deviate from the primary schema dialect.

Can I enforce a schema quality gate for .NET database reviews?

Yes, you can enforce a schema quality gate by reviewing schema changes through a step-by-step procedure that flags dialect deviations and broken versioning mechanics, generating a report with findings and severity for merge decisions.

What do I need to know to review .NET database schema quality and dialect consistency?

Reviewing .NET database schema quality requires knowledge of .NET persistence patterns and database design principles to effectively identify dialect deviations, key strategy inconsistencies, and audit column discrepancies.