القائمة
Use when the developer is adding, renaming, or changing a database field, entity, or relationship — anything that produces an EF Core migration.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when the user wants to open a pull request — e.g. "create me a PR", "open a PR", "raise a PR" — or wants to fix the description or release note on an existing PR.
Use when starting feature work, making design/product decisions, or needing the rationale or history behind a feature — checks the private companion repo for planning notes and decision records.
Use when the developer is implementing, modifying, or fixing any AI feature in this project
Use when the user wants to capture an idea, problem, or task as a PBI in the Blotz backlog — e.g. "create a PBI for this", "add this to the backlog".
Use when the developer is adding, modifying, or fixing backend API logic — endpoints, handlers, domain entities, events, or anything in `blotztask-api/`.
Use before writing, adding, or modifying any test in blotztask-test/.
| name | database-migrations |
| description | Use when the developer is adding, renaming, or changing a database field, entity, or relationship — anything that produces an EF Core migration. |
Do NOT execute dotnet ef migrations add or dotnet ef database update. Always stop and hand the command to the user to run themselves.
Explain what you changed and what the migration will produce (new tables, new columns, indexes, FK changes).
Give the user the exact command to run from blotztask-api/:
dotnet ef migrations add <MigrationName>
Tell them where the generated files will land: blotztask-api/Infrastructure/Data/Migrations/.
If the migration should then be applied to their local DB, add:
dotnet ef database update
AddLabelRelationToTaskItem, CreateTaskItemTable, RemoveSeedData.Update1 or Fix. Older entries like createDuedateToTaskItem are inconsistent — don't follow that casing.