菜单
Use when the user runs /add-migration <MigrationName> to generate, verify, and apply an EF Core migration in Timinute after an entity or model change.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/jame581/Timinute --skill add-migration命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | add-migration |
| description | Use when the user runs /add-migration <MigrationName> to generate, verify, and apply an EF Core migration in Timinute after an entity or model change. |
| disable-model-invocation | true |
Generate, verify, and locally apply a migration for Timinute.Server. The argument is the migration name (PascalCase, e.g. AddTaskNotes). If no name was given, ask for one — never invent it.
Precondition — confirm the model change is in a server entity (Timinute/Server/Models/) and the solution builds: dotnet build Timinute.sln. Client models and Shared DTOs do not affect the EF model.
Generate — the script computes paths relative to scripts/, so run it from there:
cd scripts; .\AddMigration.ps1 -name <MigrationName>; cd ..
Verify the generated migration before applying:
<timestamp>_<MigrationName>.cs + .Designer.cs under Timinute/Server/Data/Migrations/.git diff on ApplicationDbContextModelSnapshot.cs must show ONLY the intended change. Unrelated diffs = model drift — stop and investigate, do not apply.HasData in ): non-nullable columns without defaults break the SQLite test helper ( builds schema from the model + seed). Update the seed in the same commit.ApplicationDbContextEnsureCreatedAsyncApply locally — check the container first: docker ps -a --filter name=timinute.sql.server. Run .\scripts\SetupDockerSql.ps1 ONLY if it is absent — the script force-removes an existing container and wipes its data (if it exists but is stopped, docker start timinute.sql.server). Then:
cd scripts; .\MigrateDatabase.ps1; cd ..
Both scripts run dotnet tool install --global dotnet-ef unconditionally; a non-zero exit saying the tool is already installed is expected noise, not a failure.
Test — targeted first, then full:
dotnet test Timinute/Server.Tests/Timinute.Server.Tests.csproj --filter "FullyQualifiedName~<AffectedEntity>"
dotnet test Timinute.sln
Any new query over the changed columns that must translate to SQL needs a test on TestHelper.GetSqliteApplicationDbContext, not InMemory.
Docs — if the migration alters AspNetUsers or drops/renames tables, add a migration note to README's "Production deployment" section (see the v2.0/v2.1 notes there for the format). Docker deployments auto-migrate via DatabaseMigrationOnStartup=true; call out anything an operator must do manually.
Commit the entity change, migration, Designer, and snapshot together. Remind the user that the full DTO chain (Shared DTO → MappingProfile.cs → Client model) is a separate step if the new column must reach the UI.