A guided workflow for database schema changes with EF Core, .NET version upgrades, and NuGet package updates. EF Core is the .NET tool that maps application objects to database tables, while NuGet is .NET's package system.

It helps create and review database migrations, check for data loss or locking, upgrade .NET, update packages, and verify each step.

It reduces migration and upgrade risk by requiring review, testing, and a rollback plan for each logical change.

migrate — Skill for Claude Code by codewithmukesh/dotnet-claude-kit

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add codewithmukesh/dotnet-claude-kit --skill migrate

Clone the repo

git clone --depth 1 https://github.com/codewithmukesh/dotnet-claude-kit

Made for: Claude Code.

Or install dotnet-claude-kit, the plugin that ships this one along with the rest of its 51 skills, 11 agents, 2 hooks, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/codewithmukesh/dotnet-claude-kit/migrate/github.svg)](https://agentmods.dev/skills/codewithmukesh/dotnet-claude-kit/migrate)

Your own site

<a href="https://agentmods.dev/skills/codewithmukesh/dotnet-claude-kit/migrate"><img src="https://agentmods.dev/badge/skills/codewithmukesh/dotnet-claude-kit/migrate/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/codewithmukesh/dotnet-claude-kit/migrate"><img src="https://agentmods.dev/badge/skills/codewithmukesh/dotnet-claude-kit/migrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 82 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,611 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

Socket pass 17 Aug 2026
Snyk pass 17 Aug 2026
NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00082	$0.01611
Opus 5.5	$0.00033	$0.00644
Sonnet 5.5	$0.00016	$0.00322
Haiku 4.5	$0.00008	$0.00161

Measured 2mo ago against content hash 2bb388a1e0ca, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

migrate scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/migrate/SKILL.md · 183 lines

How it starts

The opening of the file, as written. The whole thing — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/migrate

What

The single migration workflow for three change types, with EF Core schema migrations as the primary flow:

EF Core schema — review pending model changes, generate a descriptively named migration, review the SQL for data loss and locking risks, apply with a documented rollback path.
.NET version upgrade — phased TFM/SDK/package upgrade with verification at each phase.
NuGet updates — incremental, one-package-at-a-time updates so breakage is always attributable.

Shared principles: verify before applying, rollback plan always, test after every step, one logical change per migration.

When

After modifying entity classes, DbContext configuration, or relationships
"add migration", "update database", "create migration", "new table", "rename column"
When generating SQL scripts for DBA review
"upgrade to .NET 10", "version upgrade", ".NET upgrade"
"upgrade nuget", "update packages", "dependency update", vulnerable package alerts

How

First, classify the request: schema change → Flow A; framework upgrade → Flow B; package update → Flow C. Then follow that flow end to end.

Flow A: EF Core Schema Migration (primary)

Step 1: Assess current state

dotnet ef migrations list --project <InfraProject> --startup-project <ApiProject>

Check for pending migrations and uncaptured model changes.

Step 2: Review model changes

Use MCP tools instead of reading whole files:

find_symbol(name: entity or DbSet)        -- locate the changed entity
get_type_hierarchy(typeName: entity)      -- check TPH/TPT/TPC inheritance changes
find_references(symbolName: property)     -- assess downstream query impact

Confirm the change is one logical unit. If not, split into multiple migrations — mixed migrations make rollback all-or-nothing.

Step 3: Generate migration

Name describes the change, not the entity: Add|Remove|Rename|Modify + WhatChanged.

# GOOD
dotnet ef migrations add AddOrderShippingAddress --project <Infra> --startup-project <Api>
# BAD — names the entity, not the change
dotnet ef migrations add Order

Read the full file on GitHub · 183 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 183 lines · 82 tokens per session scan A 2bb388a1e0ca

Subscribe to this mod's changes

migrate is a skill published in the GitHub repository codewithmukesh/dotnet-claude-kit (805 stars, last pushed 2d ago), licensed MIT. It adds 82 tokens to every session and 1,611 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

C# and .NET Databases Languages

migrate next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
migratecodewithmukesh/dotnet-claude-kit	Skill	805	2d ago	MIT	A	82	Claude Code
optimizing-ef-core-queriesdotnet/skills	Skill	5.8k	yesterday	MIT	A	116	Claude Code
azure-resource-manager-postgresql-dotnetmicrosoft/skills	Skill	3.2k	yesterday	MIT	A	97	Claude Code
efcore-patternsAaronontheweb/dotnet-skills	Skill	1.3k	9d ago	MIT	A	35	Claude Code
entity-framework-coremanagedcode/dotnet-skills	Skill	508	yesterday	MIT	A	110	Claude Code, Codex
entity-framework6managedcode/dotnet-skills	Skill	508	yesterday	MIT	A	114	Claude Code, Codex
neo4j-driver-dotnet-skillneo4j-contrib/neo4j-skills	Skill	120	4d ago	MIT	A	187	Claude Code