メニュー
Create an EF Core migration for a specific microservice. Use after adding or modifying entities, DbSets, or entity configurations — migration creation is mandatory for any schema change.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Verify hexagonal architecture layer rules, Result pattern usage, and coding conventions. Use as a quick local check during development — fast and focused on architecture rules only. For full security + quality review, use /code-review instead.
Review code changes for security, architecture, and quality issues. Use for deep PR-level review — checks OWASP vulnerabilities, hexagonal architecture violations, code smells, and test gaps. For a quick architecture-only check, use /check-architecture instead.
Complete current task with all quality gates, code review, QA check, and submit PR. Use when implementation is done and you want to run the full verification pipeline (build, lint, tests, review, QA) and create the pull request.
Complete infrastructure task — lint, validate, review, and submit PR. Use when an infrastructure-only branch is ready for submission — runs Terraform/Helm validation and creates the PR, skipping .NET/frontend checks.
Scaffold a new frontend feature module with page, components, API service, and hooks. Use whenever the user wants to add a new page, dashboard section, UI module, or frontend feature to the React app.
Capture a screenshot of a URL or route with one command. Use whenever the user wants to take a screenshot, capture a page, see what a route looks like, or visually verify a page. Supports mobile viewport with --mobile and unauthenticated mode with --no-auth.
| name | add-migration |
| description | Create an EF Core migration for a specific microservice. Use after adding or modifying entities, DbSets, or entity configurations — migration creation is mandatory for any schema change. |
| allowed-tools | Bash, Read, Glob, Grep |
| user-invocable | true |
Create a new EF Core migration for a microservice's database context.
{Name} — Migration name in PascalCase (e.g., AddDeviceTagsTable){Service} — Target microservice (ask if ambiguous)| Service | Infrastructure Project | DbContext |
|---|---|---|
| DeviceManager | src/DeviceManager/SignalBeam.DeviceManager.Infrastructure | DeviceManagerDbContext |
| BundleOrchestrator | src/BundleOrchestrator/BundleOrchestrator.Infrastructure | BundleOrchestratorDbContext |
| TelemetryProcessor | src/TelemetryProcessor/TelemetryProcessor.Infrastructure | TelemetryProcessorDbContext |
| IdentityManager | src/IdentityManager/SignalBeam.IdentityManager.Infrastructure | IdentityDbContext |
Before creating a migration, check that entity configurations are in place:
# Find the entity configuration
grep -rn "IEntityTypeConfiguration" src/{Service}/
Run from the Infrastructure project directory:
dotnet ef migrations add {Name} \
--project src/{Service}/{Service}.Infrastructure \
--startup-project src/{Service}/{Service}.Host \
--output-dir Persistence/Migrations
If the startup project differs from the convention, search for the .Host project:
find src/{Service} -name "*.Host.csproj" -o -name "*.Host" -type d
Read the generated migration file and verify:
# Find the latest migration
ls -t src/{Service}/**/Migrations/*.cs | head -2
Only apply if the user explicitly asks:
dotnet ef database update \
--project src/{Service}/{Service}.Infrastructure \
--startup-project src/{Service}/{Service}.Host
dotnet tool install --global dotnet-ef and retry.dotnet build on the Host project first to surface errors./add-entity to create the entity and EF Core configuration first/run-tests to verify tests still pass after migration