Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From zzaia-workspace
Entity Framework Core migrations management across repositories
npx claudepluginhub zzaia/zzaia-agentic-workspace --plugin zzaia-workspaceHow this command is triggered — by the user, by Claude, or both
Slash command
/zzaia-workspace:migrations --repository <name> --branch <name> --action add|remove|list|update|script|drop [--migration <name>] [--description <text>]commands/behavior/development/The summary Claude sees in its command listing — used to decide when to auto-load this command
## PURPOSE Manage Entity Framework Core database migrations with standardized actions and security best practices. ## EXECUTION - **CRITICAL**: Always apply migrations in the .Data project or in the project where the DbContext is implemented - NEVER apply migrations in the main application where appsettings are located - This is a security measure to prevent direct database modifications in the primary application layer 1. **Validation Phase** - Verify repository and branch existence - Check EF Core project configuration - Validate migration action permissions 2. **Migration ...
Share bugs, ideas, or general feedback.
Manage Entity Framework Core database migrations with standardized actions and security best practices.
Validation Phase
Migration Preparation
Migration Execution
Direct EF Core migration management with comprehensive validation and security measures.
sequenceDiagram
participant U as User
participant C as /migrations Command
participant W as Workspace
participant EF as EF Core
participant DB as Database
U->>C: /migrations <repo> <branch> <action> [name]
C->>W: Validate repository and branch
W-->>C: Repository context
C->>EF: Check current database state
C->>EF: Execute migration action
EF->>DB: Apply changes (if applicable)
DB-->>EF: Database response
EF-->>C: Migration results
C-->>U: Migration execution summary
repository: Git repository name containing the EF Core projectbranch: Specific branch for migration executionaction: Migration operation type
add: Create new migration capturing model changesremove: Remove last migrationlist: List all migrationsupdate: Apply pending migrations to databasescript: Generate SQL migration scriptdrop: Drop database (caution)migration-name: Optional descriptive name for migration (recommended for add action)# Add a new migration
/migrations compliance-hub main add AddUserProfile
# Update database to latest migration
/migrations customer-portal develop update
# List all migrations
/migrations identity-service feature/auth list
# Generate SQL script
/migrations my-project main script