Menú
Build the SQL Server DACPAC and scaffold EF Core entities. Run this after finishing all SQL schema edits in Neptune.Database/.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | db-build-scaffold |
| description | Build the SQL Server DACPAC and scaffold EF Core entities. Run this after finishing all SQL schema edits in Neptune.Database/. |
| allowed-tools | ["Bash(powershell*DatabaseBuild*)","Bash(powershell*Scaffold*)","Bash(git diff*)"] |
Deploy database schema changes and regenerate EF Core entities to keep the C# model layer in sync with the database.
Run /db-build-scaffold after you have finished editing SQL files in Neptune.Database/. Batch your SQL edits first, then run this once.
Build and deploy the DACPAC to the local SQL Server:
cd C:/git/esassoc/neptune/Build && powershell.exe -ExecutionPolicy Bypass -File DatabaseBuild.ps1
Build/ directory so PowerShell module imports resolve correctly.Scaffold EF Core entities from the updated database:
cd C:/git/esassoc/neptune/Build && powershell.exe -ExecutionPolicy Bypass -File Scaffold.ps1
Neptune.EFModels/Entities/Generated/.Report what changed by running:
git diff --stat Neptune.EFModels/Entities/Generated/
Summarize the regenerated entity files so the user knows what was updated.
Build/ directory — they use relative module imports that fail from other directories./codegen if the schema changes affect API DTOs or endpoints.Neptune.EFModels/Entities/Generated/ should not be edited directly — they are overwritten by the scaffold.Create or flesh out a Jira story with structured sections for POs, Devs, and Claude. Accepts an optional Jira key to update an existing card.
Export Water Quality Management Plans for one jurisdiction from the local Neptune database to an Esri File Geodatabase in native projection. Use when a client requests WQMP spatial data for a specific city/jurisdiction.
Extract rework items from a Jira card's Acceptance Criteria and produce a fix plan. Auto-detects issue key from branch or accepts one as argument.
Fetch a Jira card by key (e.g. NPT-100) and produce a detailed implementation plan. Use this when starting work on a new story.
Add a scrollspy Table of Contents sidebar to a page component with signal-based scroll tracking.
Audit migration progress from legacy MVC to Angular SPA. Reports which entities are migrated, partial, or not started.