@atlashub/smartstack-cli 3.39.0 → 3.41.0

package/templates/skills/efcore/SKILL.md

@@ -1,167 +1,168 @@
----
-name: efcore
-description: EF Core Commands - Migration and database management
-argument-hint: "<command> [options]"
-disable-model-invocation: true
----
-
-## Current state (auto-injected)
-- Branch: !`git branch --show-current`
-- Recent migrations: _(detected in step-00-init)_
-
-<objective>
-Manage EF Core migrations and database operations with progressive step loading, MCP validation, and DbContext auto-detection.
-</objective>
-
-<quick_start>
-**Database operations:**
-```bash
-/efcore db-status          # Check migration status
-/efcore db-deploy          # Apply pending migrations
-/efcore db-reset           # Drop + recreate database
-/efcore db-seed            # Populate with test data
-```
-
-**Migration operations:**
-```bash
-/efcore migration          # Create migration for current branch
-/efcore squash             # Consolidate branch migrations
-/efcore rebase-snapshot    # Sync snapshot with parent branch
-/efcore scan               # Scan for cross-branch conflicts
-/efcore conflicts          # Analyze migration conflicts
-```
-</quick_start>
-
-<parameters>
-
-<subcommands>
-| Command | Description | Steps |
-|---------|-------------|-------|
-| `db-status` | Display migrations and database status | steps/db/status/ |
-| `db-deploy` | Apply pending migrations | steps/db/deploy/ |
-| `db-reset` | Drop + recreate database | steps/db/reset/ |
-| `db-seed` | Populate with test data | steps/db/seed/ |
-| `migration` | Create/recreate migration | steps/migration/ |
-| `squash` | Consolidate migrations | steps/squash/ |
-| `rebase-snapshot` | Sync snapshot with parent | steps/rebase-snapshot/ |
-| `scan` | Scan for conflicts | (MCP-centric) |
-| `conflicts` | Analyze conflicts | (MCP-centric) |
-</subcommands>
-
-<flags>
-| Flag | Description |
-|------|-------------|
-| `--context <name>` | Specify DbContext (CoreDbContext/ExtensionsDbContext) |
-| `--env <name>` | Use appsettings.{name}.json |
-| `--verbose` | Show detailed output |
-| `--force` | Skip confirmations |
-| `--dry-run` | Preview without executing |
-</flags>
-
-</parameters>
-
-<state_variables>
-**Shared state across all steps:**
-
-| Variable | Type | Description |
-|----------|------|-------------|
-| `{command}` | string | Current subcommand |
-| `{dbcontext}` | string | CoreDbContext or ExtensionsDbContext |
-| `{dbcontext_type}` | string | "core" or "extensions" |
-| `{schema}` | string | Database schema |
-| `{infra_project}` | string | Path to Infrastructure project |
-| `{startup_project}` | string | Path to API/Web project |
-| `{migrations_dir}` | string | Path to Migrations folder |
-| `{base_branch}` | string | Parent branch (develop/main) |
-| `{branch_type}` | string | feature/release/hotfix |
-| `{auto_mode}` | boolean | Skip confirmations |
-</state_variables>
-
-<entry_point>
-
-**ROUTING LOGIC:**
-
-1. Parse command and flags from input
-2. Load shared init step: `steps/shared/step-00-init.md`
-3. Route to command-specific steps:
-
-| Command | Route To |
-|---------|----------|
-| `db-status` | `steps/db/step-status.md` |
-| `db-deploy` | `steps/db/step-deploy.md` |
-| `db-reset` | `steps/db/step-reset.md` |
-| `db-seed` | `steps/db/step-seed.md` |
-| `migration` | `steps/migration/step-00-init.md` |
-| `squash` | `steps/squash/step-00-init.md` |
-| `rebase-snapshot` | `steps/rebase-snapshot/step-00-init.md` |
-| `scan` | Use `commands/efcore/scan.md` (MCP-centric, no steps) |
-| `conflicts` | Use `commands/efcore/conflicts.md` (MCP-centric, no steps) |
-
-</entry_point>
-
-<shared_functions>
-**Always load first:** `steps/shared/step-00-init.md`
-
-This step provides:
-- `detect_efcore_project()` - Find EF Core project files
-- `detect_dbcontext()` - Auto-detect Core vs Extensions
-- `detect_environment()` - Load connection string
-- `determine_base_branch()` - Find parent branch
-- `block_production()` - Safety check
-
-**MCP Integration:**
-- `mcp__smartstack__suggest_migration` - Generate compliant names
-- `mcp__smartstack__check_migrations` - Analyze conflicts
-- `mcp__smartstack__validate_conventions` - Validate structure
-</shared_functions>
-
-<dual_dbcontext>
-SmartStack uses **two separate DbContexts**:
-
-| Context | DbContext | Schema | History Table |
-|---------|-----------|--------|---------------|
-| `core` | `CoreDbContext` | `core` | `core.__EFMigrationsHistory` |
-| `extensions` | `ExtensionsDbContext` | `extensions` | `extensions.__EFMigrationsHistory` |
-
-**Auto-detection priority:**
-1. SmartStack.Domain exists → CoreDbContext
-2. Client with SmartStack NuGet → ExtensionsDbContext
-3. Code scan for DbContext classes
-4. Ask user if ambiguous
-</dual_dbcontext>
-
-<naming_convention>
-**Migration naming (MCP MANDATORY):**
-
-Pattern: `{context}_v{version}_{sequence}_{Description}`
-
-Examples:
-- `core_v1.9.0_001_AddUserRoles`
-- `extensions_v1.2.0_001_AddCustomFields`
-
-**FORBIDDEN:** Manual name calculation. Always use MCP.
-</naming_convention>
-
-<safety_rules>
-1. **Backup MANDATORY** for destructive operations
-2. **Production BLOCKED** - Never run on production
-3. **1 migration per feature** - Recreate, don't accumulate
-4. **Snapshot + Migrations** - Always recover BOTH from parent
-5. **MCP for naming** - Never hardcode migration names
-</safety_rules>
-
-<execution_rules>
-- **Load one step at a time** - Progressive loading
-- **State persists** - Variables carry across steps
-- **Follow next_step** - Each step defines next
-- **MCP validation** - Use SmartStack tools
-- **Safety > Correctness > Speed**
-</execution_rules>
-
-<success_criteria>
-- DbContext correctly detected
-- Migrations created with MCP naming
-- Database operations succeed
-- Parent migrations preserved (for squash/rebase)
-- Build passes after changes
-</success_criteria>
+---
+name: efcore
+description: EF Core Commands - Migration and database management
+argument-hint: "<command> [options]"
+disable-model-invocation: true
+---
+
+## Current state (auto-injected)
+- Preflight: !`if [ -f .git ] && grep -q '^gitdir: [A-Za-z]:' .git 2>/dev/null && grep -qi microsoft /proc/version 2>/dev/null; then p=$(sed 's/^gitdir: //' .git | tr -d '\r\n'); d=$(echo "${p:0:1}" | tr A-Z a-z); r="${p:2}"; r="${r//\\//}"; printf 'gitdir: %s\n' "$(realpath -m --relative-to="$(pwd)" "/mnt/$d$r")" > .git && echo "repaired"; else echo "ok"; fi`
+- Branch: !`git branch --show-current 2>/dev/null || echo "UNAVAILABLE"`
+- Recent migrations: _(detected in step-00-init)_
+
+<objective>
+Manage EF Core migrations and database operations with progressive step loading, MCP validation, and DbContext auto-detection.
+</objective>
+
+<quick_start>
+**Database operations:**
+```bash
+/efcore db-status          # Check migration status
+/efcore db-deploy          # Apply pending migrations
+/efcore db-reset           # Drop + recreate database
+/efcore db-seed            # Populate with test data
+```
+
+**Migration operations:**
+```bash
+/efcore migration          # Create migration for current branch
+/efcore squash             # Consolidate branch migrations
+/efcore rebase-snapshot    # Sync snapshot with parent branch
+/efcore scan               # Scan for cross-branch conflicts
+/efcore conflicts          # Analyze migration conflicts
+```
+</quick_start>
+
+<parameters>
+
+<subcommands>
+| Command | Description | Steps |
+|---------|-------------|-------|
+| `db-status` | Display migrations and database status | steps/db/status/ |
+| `db-deploy` | Apply pending migrations | steps/db/deploy/ |
+| `db-reset` | Drop + recreate database | steps/db/reset/ |
+| `db-seed` | Populate with test data | steps/db/seed/ |
+| `migration` | Create/recreate migration | steps/migration/ |
+| `squash` | Consolidate migrations | steps/squash/ |
+| `rebase-snapshot` | Sync snapshot with parent | steps/rebase-snapshot/ |
+| `scan` | Scan for conflicts | (MCP-centric) |
+| `conflicts` | Analyze conflicts | (MCP-centric) |
+</subcommands>
+
+<flags>
+| Flag | Description |
+|------|-------------|
+| `--context <name>` | Specify DbContext (CoreDbContext/ExtensionsDbContext) |
+| `--env <name>` | Use appsettings.{name}.json |
+| `--verbose` | Show detailed output |
+| `--force` | Skip confirmations |
+| `--dry-run` | Preview without executing |
+</flags>
+
+</parameters>
+
+<state_variables>
+**Shared state across all steps:**
+
+| Variable | Type | Description |
+|----------|------|-------------|
+| `{command}` | string | Current subcommand |
+| `{dbcontext}` | string | CoreDbContext or ExtensionsDbContext |
+| `{dbcontext_type}` | string | "core" or "extensions" |
+| `{schema}` | string | Database schema |
+| `{infra_project}` | string | Path to Infrastructure project |
+| `{startup_project}` | string | Path to API/Web project |
+| `{migrations_dir}` | string | Path to Migrations folder |
+| `{base_branch}` | string | Parent branch (develop/main) |
+| `{branch_type}` | string | feature/release/hotfix |
+| `{auto_mode}` | boolean | Skip confirmations |
+</state_variables>
+
+<entry_point>
+
+**ROUTING LOGIC:**
+
+1. Parse command and flags from input
+2. Load shared init step: `steps/shared/step-00-init.md`
+3. Route to command-specific steps:
+
+| Command | Route To |
+|---------|----------|
+| `db-status` | `steps/db/step-status.md` |
+| `db-deploy` | `steps/db/step-deploy.md` |
+| `db-reset` | `steps/db/step-reset.md` |
+| `db-seed` | `steps/db/step-seed.md` |
+| `migration` | `steps/migration/step-00-init.md` |
+| `squash` | `steps/squash/step-00-init.md` |
+| `rebase-snapshot` | `steps/rebase-snapshot/step-00-init.md` |
+| `scan` | Use `commands/efcore/scan.md` (MCP-centric, no steps) |
+| `conflicts` | Use `commands/efcore/conflicts.md` (MCP-centric, no steps) |
+
+</entry_point>
+
+<shared_functions>
+**Always load first:** `steps/shared/step-00-init.md`
+
+This step provides:
+- `detect_efcore_project()` - Find EF Core project files
+- `detect_dbcontext()` - Auto-detect Core vs Extensions
+- `detect_environment()` - Load connection string
+- `determine_base_branch()` - Find parent branch
+- `block_production()` - Safety check
+
+**MCP Integration:**
+- `mcp__smartstack__suggest_migration` - Generate compliant names
+- `mcp__smartstack__check_migrations` - Analyze conflicts
+- `mcp__smartstack__validate_conventions` - Validate structure
+</shared_functions>
+
+<dual_dbcontext>
+SmartStack uses **two separate DbContexts**:
+
+| Context | DbContext | Schema | History Table |
+|---------|-----------|--------|---------------|
+| `core` | `CoreDbContext` | `core` | `core.__EFMigrationsHistory` |
+| `extensions` | `ExtensionsDbContext` | `extensions` | `extensions.__EFMigrationsHistory` |
+
+**Auto-detection priority:**
+1. SmartStack.Domain exists → CoreDbContext
+2. Client with SmartStack NuGet → ExtensionsDbContext
+3. Code scan for DbContext classes
+4. Ask user if ambiguous
+</dual_dbcontext>
+
+<naming_convention>
+**Migration naming (MCP MANDATORY):**
+
+Pattern: `{context}_v{version}_{sequence}_{Description}`
+
+Examples:
+- `core_v1.9.0_001_AddUserRoles`
+- `extensions_v1.2.0_001_AddCustomFields`
+
+**FORBIDDEN:** Manual name calculation. Always use MCP.
+</naming_convention>
+
+<safety_rules>
+1. **Backup MANDATORY** for destructive operations
+2. **Production BLOCKED** - Never run on production
+3. **1 migration per feature** - Recreate, don't accumulate
+4. **Snapshot + Migrations** - Always recover BOTH from parent
+5. **MCP for naming** - Never hardcode migration names
+</safety_rules>
+
+<execution_rules>
+- **Load one step at a time** - Progressive loading
+- **State persists** - Variables carry across steps
+- **Follow next_step** - Each step defines next
+- **MCP validation** - Use SmartStack tools
+- **Safety > Correctness > Speed**
+</execution_rules>
+
+<success_criteria>
+- DbContext correctly detected
+- Migrations created with MCP naming
+- Database operations succeed
+- Parent migrations preserved (for squash/rebase)
+- Build passes after changes
+</success_criteria>

package/templates/skills/efcore/references/both-contexts.md

@@ -1,32 +1,32 @@
-# Both Contexts Deployment
-
-When `RUN_BOTH=true` (auto-detected for client projects with SmartStack NuGet):
-
-```bash
-# 1. Deploy CoreDbContext first (system tables: Users, Roles, Tenants...)
-echo "=== Deploying CoreDbContext (core schema) ==="
-DBCONTEXT="CoreDbContext"
-SCHEMA="core"
-# Run steps 2-6 with CoreDbContext...
-
-dotnet ef database update \
-  --context "CoreDbContext" \
-  --project "$INFRA_PROJECT" \
-  --startup-project "$STARTUP_PROJECT" \
-  --verbose
-
-# 2. Then ExtensionsDbContext (client tables)
-echo ""
-echo "=== Deploying ExtensionsDbContext (extensions schema) ==="
-DBCONTEXT="ExtensionsDbContext"
-SCHEMA="extensions"
-# Run steps 2-6 with ExtensionsDbContext...
-
-dotnet ef database update \
-  --context "ExtensionsDbContext" \
-  --project "$INFRA_PROJECT" \
-  --startup-project "$STARTUP_PROJECT" \
-  --verbose
-```
-
-**Order matters:** Core MUST be deployed first (Extensions may have foreign keys to Core tables).
+# Both Contexts Deployment
+
+When `RUN_BOTH=true` (auto-detected for client projects with SmartStack NuGet):
+
+```bash
+# 1. Deploy CoreDbContext first (system tables: Users, Roles, Tenants...)
+echo "=== Deploying CoreDbContext (core schema) ==="
+DBCONTEXT="CoreDbContext"
+SCHEMA="core"
+# Run steps 2-6 with CoreDbContext...
+
+dotnet ef database update \
+  --context "CoreDbContext" \
+  --project "$INFRA_PROJECT" \
+  --startup-project "$STARTUP_PROJECT" \
+  --verbose
+
+# 2. Then ExtensionsDbContext (client tables)
+echo ""
+echo "=== Deploying ExtensionsDbContext (extensions schema) ==="
+DBCONTEXT="ExtensionsDbContext"
+SCHEMA="extensions"
+# Run steps 2-6 with ExtensionsDbContext...
+
+dotnet ef database update \
+  --context "ExtensionsDbContext" \
+  --project "$INFRA_PROJECT" \
+  --startup-project "$STARTUP_PROJECT" \
+  --verbose
+```
+
+**Order matters:** Core MUST be deployed first (Extensions may have foreign keys to Core tables).

package/templates/skills/efcore/references/database-operations.md

@@ -1,67 +1,67 @@
-# Database Operations
-
-## Common Validation Checks
-
-### Check Required Variables
-
-```bash
-# Validate required variables from step-00-init
-for VAR_NAME in DBCONTEXT DBCONTEXT_TYPE INFRA_PROJECT STARTUP_PROJECT SELECTED_ENV; do
-  eval VAR_VALUE=\$$VAR_NAME
-  if [ -z "$VAR_VALUE" ]; then
-    echo "ERROR: Required variable $VAR_NAME is not set"
-    echo "Run step-00-init first"
-    exit 1
-  fi
-done
-```
-
-## Backup Command
-
-```bash
-BACKUP_DIR=".claude/gitflow/backup/database"
-mkdir -p "$BACKUP_DIR"
-
-BACKUP_FILE="$BACKUP_DIR/${DATABASE_NAME}_$(date +%Y%m%d_%H%M%S).bak"
-
-echo "Creating backup: $BACKUP_FILE"
-
-sqlcmd -S "$SERVER_NAME" -E -Q "BACKUP DATABASE [$DATABASE_NAME] TO DISK='$BACKUP_FILE'"
-
-if [ $? -eq 0 ]; then
-  echo "Backup created: $BACKUP_FILE"
-else
-  echo "WARNING: Backup failed. Continue anyway?"
-fi
-```
-
-## Connection Test
-
-```bash
-CONNECTION_TEST=$(dotnet ef database list \
-  --context "$DBCONTEXT" \
-  --project "$INFRA_PROJECT" \
-  --startup-project "$STARTUP_PROJECT" 2>&1)
-
-if [ $? -eq 0 ]; then
-  echo "Connection:  OK"
-else
-  echo "Connection:  FAILED"
-  echo ""
-  echo "$CONNECTION_TEST"
-fi
-```
-
-## Migration Count Utilities
-
-```bash
-# Count applied and pending
-MIGRATION_OUTPUT=$(dotnet ef migrations list \
-  --context "$DBCONTEXT" \
-  --project "$INFRA_PROJECT" \
-  --startup-project "$STARTUP_PROJECT" 2>/dev/null)
-
-APPLIED=$(echo "$MIGRATION_OUTPUT" | grep -v "(Pending)" | grep -c "^[0-9]" || echo "0")
-PENDING=$(echo "$MIGRATION_OUTPUT" | grep -c "(Pending)" || echo "0")
-TOTAL=$((APPLIED + PENDING))
-```
+# Database Operations
+
+## Common Validation Checks
+
+### Check Required Variables
+
+```bash
+# Validate required variables from step-00-init
+for VAR_NAME in DBCONTEXT DBCONTEXT_TYPE INFRA_PROJECT STARTUP_PROJECT SELECTED_ENV; do
+  eval VAR_VALUE=\$$VAR_NAME
+  if [ -z "$VAR_VALUE" ]; then
+    echo "ERROR: Required variable $VAR_NAME is not set"
+    echo "Run step-00-init first"
+    exit 1
+  fi
+done
+```
+
+## Backup Command
+
+```bash
+BACKUP_DIR=".claude/gitflow/backup/database"
+mkdir -p "$BACKUP_DIR"
+
+BACKUP_FILE="$BACKUP_DIR/${DATABASE_NAME}_$(date +%Y%m%d_%H%M%S).bak"
+
+echo "Creating backup: $BACKUP_FILE"
+
+sqlcmd -S "$SERVER_NAME" -E -Q "BACKUP DATABASE [$DATABASE_NAME] TO DISK='$BACKUP_FILE'"
+
+if [ $? -eq 0 ]; then
+  echo "Backup created: $BACKUP_FILE"
+else
+  echo "WARNING: Backup failed. Continue anyway?"
+fi
+```
+
+## Connection Test
+
+```bash
+CONNECTION_TEST=$(dotnet ef database list \
+  --context "$DBCONTEXT" \
+  --project "$INFRA_PROJECT" \
+  --startup-project "$STARTUP_PROJECT" 2>&1)
+
+if [ $? -eq 0 ]; then
+  echo "Connection:  OK"
+else
+  echo "Connection:  FAILED"
+  echo ""
+  echo "$CONNECTION_TEST"
+fi
+```
+
+## Migration Count Utilities
+
+```bash
+# Count applied and pending
+MIGRATION_OUTPUT=$(dotnet ef migrations list \
+  --context "$DBCONTEXT" \
+  --project "$INFRA_PROJECT" \
+  --startup-project "$STARTUP_PROJECT" 2>/dev/null)
+
+APPLIED=$(echo "$MIGRATION_OUTPUT" | grep -v "(Pending)" | grep -c "^[0-9]" || echo "0")
+PENDING=$(echo "$MIGRATION_OUTPUT" | grep -c "(Pending)" || echo "0")
+TOTAL=$((APPLIED + PENDING))
+```

package/templates/skills/efcore/references/destructive-operations.md

@@ -1,38 +1,38 @@
-# Destructive Operations & Zero-Downtime Patterns
-
-When a migration contains destructive operations (DropColumn, RenameColumn, AlterColumn, DropTable), consider zero-downtime patterns for production deployments.
-
-## Detection
-
-Migration Analysis counts:
-- DropColumn
-- RenameColumn
-- AlterColumn
-- DropTable
-
-If any count > 0, display warning and reference this document.
-
-## Zero-Downtime Patterns
-
-For production deployments with destructive operations:
-
-1. **Add → Populate → Migrate → Remove** (for column renames)
-   - Add new column
-   - Populate from old column
-   - Deploy migration
-   - Remove old column in next deployment window
-
-2. **Feature Flags** (for table changes)
-   - Add feature flag
-   - Deploy new code path
-   - Migrate data
-   - Remove old code path after stabilization
-
-3. **Gradual Rollout**
-   - Deploy to staging first
-   - Monitor for issues
-   - Gradually roll to production clusters
-
-## Reference
-
-See OWASP and database migration best practices for your platform.
+# Destructive Operations & Zero-Downtime Patterns
+
+When a migration contains destructive operations (DropColumn, RenameColumn, AlterColumn, DropTable), consider zero-downtime patterns for production deployments.
+
+## Detection
+
+Migration Analysis counts:
+- DropColumn
+- RenameColumn
+- AlterColumn
+- DropTable
+
+If any count > 0, display warning and reference this document.
+
+## Zero-Downtime Patterns
+
+For production deployments with destructive operations:
+
+1. **Add → Populate → Migrate → Remove** (for column renames)
+   - Add new column
+   - Populate from old column
+   - Deploy migration
+   - Remove old column in next deployment window
+
+2. **Feature Flags** (for table changes)
+   - Add feature flag
+   - Deploy new code path
+   - Migrate data
+   - Remove old code path after stabilization
+
+3. **Gradual Rollout**
+   - Deploy to staging first
+   - Monitor for issues
+   - Gradually roll to production clusters
+
+## Reference
+
+See OWASP and database migration best practices for your platform.