dotnet-data
Overview
Use this skill for .NET data-access work, especially Entity Framework Core modeling, migrations, queries, transactions, and repository data-flow analysis using guidance from dotnet/skills.
Workflow
- Identify DbContext types, migrations, provider packages, connection configuration, and data-access boundaries.
- Preserve schema compatibility, migration history, query semantics, and transaction behavior.
- Use EF Core tooling and tests where available to verify model and migration changes.
- Explain data-shape, performance, and compatibility risks explicitly.
Guardrails
- Do not generate destructive migrations without user approval.
- Avoid changing persisted schema, indexes, or cascade behavior as an incidental side effect.
- Keep provider-specific behavior visible when SQL Server, PostgreSQL, SQLite, Cosmos, or other providers differ.
Expected Output
Return focused data-access changes or guidance with schema impact, validation commands, and any migration notes.
1---2name: dotnet-data3description: "Skills for .NET data access and Entity Framework related tasks."4license: MIT5metadata:6 author: dotnet7 version: "1.0.0"8 source: https://github.com/dotnet/skills/tree/main/plugins/dotnet-data9---1011# dotnet-data1213## Overview1415Use this skill for .NET data-access work, especially Entity Framework Core modeling, migrations, queries, transactions, and repository data-flow analysis using guidance from [dotnet/skills](https://github.com/dotnet/skills).1617## Workflow18191. Identify DbContext types, migrations, provider packages, connection configuration, and data-access boundaries.202. Preserve schema compatibility, migration history, query semantics, and transaction behavior.213. Use EF Core tooling and tests where available to verify model and migration changes.224. Explain data-shape, performance, and compatibility risks explicitly.2324## Guardrails2526- Do not generate destructive migrations without user approval.27- Avoid changing persisted schema, indexes, or cascade behavior as an incidental side effect.28- Keep provider-specific behavior visible when SQL Server, PostgreSQL, SQLite, Cosmos, or other providers differ.2930## Expected Output3132Return focused data-access changes or guidance with schema impact, validation commands, and any migration notes.
autohandai