Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

create-migration

Create and manage Entity Framework Core database migrations including schema changes, seed data, and rollback strategies. Use when adding or modifying EF Core entities, setting up a new DbContext, applying data seeding, running dotnet ef commands, or troubleshooting migration conflicts.

Executar no Manus

Visão geral

Comando de instalação

npx skills add https://github.com/andresharpe/dotbot --skill create-migration

Copie e cole este comando no Claude Code para instalar a skill

Fonte

andresharpe/dotbot

Estrelas51

Forks25

Atualizado3 de abril de 2026 às 16:35

SKILL.md

readonly

name	create-migration
description	Create and manage Entity Framework Core database migrations including schema changes, seed data, and rollback strategies. Use when adding or modifying EF Core entities, setting up a new DbContext, applying data seeding, running dotnet ef commands, or troubleshooting migration conflicts.

Create EF Migration

Create, review, and apply Entity Framework Core migrations safely.

Workflow

Make entity/model changes in code
Generate migration with a descriptive name
Review the generated migration — verify no unintended column drops or data loss
Apply to local database and verify
Commit migration files with the related entity changes

Creating Migrations

# Generate a new migration (from the project directory containing the DbContext)
dotnet ef migrations add AddInvoiceLineItems --project src/MyApp.Data --startup-project src/MyApp.Api

# Apply to local database
dotnet ef database update --project src/MyApp.Data --startup-project src/MyApp.Api

# Rollback to a previous migration
dotnet ef database update PreviousMigrationName --project src/MyApp.Data --startup-project src/MyApp.Api

# Remove the last unapplied migration
dotnet ef migrations remove --project src/MyApp.Data --startup-project src/MyApp.Api

Best Practices

Descriptive names: AddInvoiceLineItems, RenameUserEmailToContactEmail — never Update1
Small and focused: One schema change per migration for easier rollback
Seed data: Use HasData() in OnModelCreating or IEntityTypeConfiguration<T>, not raw SQL in migrations
Review before applying: Check the generated Up() and Down() methods for unintended drops or data loss
Test locally: Always apply against a local database before committing

Checklist

Migration has a descriptive, intention-revealing name
Generated Up() and Down() methods reviewed for correctness
No unintended column drops or data loss
Migration applied successfully to local database
Seed data uses HasData(), not raw SQL
Migration files committed alongside entity changes

Mais deste repositório

mesmo repositório

design-system

andresharpe/dotbot

Dotbot CRT/retro-futuristic design system: tokens, components, patterns, and anti-patterns for the control panel UI.

2026-04-2751

blazor-component-design

andresharpe/dotbot

Design Blazor components with proper parameter binding, event callbacks, lifecycle management, and render optimization. Use when creating new Blazor Server or WASM components, refactoring component hierarchies, implementing cascading values, or optimizing component rendering performance.

2026-04-0351

entity-design

andresharpe/dotbot

Design EF Core entities with navigation properties, value objects, Fluent API configuration, and audit fields. Use when creating new database entities, adding relationships, configuring owned types, designing a domain model for Entity Framework Core, or setting up table-per-hierarchy inheritance.

2026-04-0351

create-migration

andresharpe/dotbot

Create and manage database migrations with Entity Framework Core, including schema changes, data seeding, and rollback strategies

2026-04-0351

entity-design

andresharpe/dotbot

Design and document domain entities with consistent structure, relationships, and audit fields following project conventions

2026-04-0351

implement-api-endpoint

andresharpe/dotbot

Implement ASP.NET Core REST API endpoints with routing, validation, MediatR handlers, and proper HTTP status codes. Use when creating new API routes, adding HTTP endpoints, building RESTful resources, implementing controllers, or adding GET/POST/PUT/DELETE operations.

2026-04-0351

Fonte

andresharpe

andresharpe/dotbot

Abrir repositório GitHub Ver repositórios do creator

Comando de instalação

Download

Executar no Manus

Útil paraSOC

Arquitetos de banco de dadosInformática e Matemática15-1243L4

name	create-migration
description	Create and manage Entity Framework Core database migrations including schema changes, seed data, and rollback strategies. Use when adding or modifying EF Core entities, setting up a new DbContext, applying data seeding, running dotnet ef commands, or troubleshooting migration conflicts.

Create EF Migration

Create, review, and apply Entity Framework Core migrations safely.

Workflow

Make entity/model changes in code
Generate migration with a descriptive name
Review the generated migration — verify no unintended column drops or data loss
Apply to local database and verify
Commit migration files with the related entity changes

Creating Migrations

# Generate a new migration (from the project directory containing the DbContext)
dotnet ef migrations add AddInvoiceLineItems --project src/MyApp.Data --startup-project src/MyApp.Api

# Apply to local database
dotnet ef database update --project src/MyApp.Data --startup-project src/MyApp.Api

# Rollback to a previous migration
dotnet ef database update PreviousMigrationName --project src/MyApp.Data --startup-project src/MyApp.Api

# Remove the last unapplied migration
dotnet ef migrations remove --project src/MyApp.Data --startup-project src/MyApp.Api

Best Practices

Descriptive names: AddInvoiceLineItems, RenameUserEmailToContactEmail — never Update1
Small and focused: One schema change per migration for easier rollback
Seed data: Use HasData() in OnModelCreating or IEntityTypeConfiguration<T>, not raw SQL in migrations
Review before applying: Check the generated Up() and Down() methods for unintended drops or data loss
Test locally: Always apply against a local database before committing

Checklist

Migration has a descriptive, intention-revealing name
Generated Up() and Down() methods reviewed for correctness
No unintended column drops or data loss
Migration applied successfully to local database
Seed data uses HasData(), not raw SQL
Migration files committed alongside entity changes