@atlashub/smartstack-cli 4.35.0 → 4.37.0

package/templates/skills/efcore/steps/db/step-reset.md

@@ -1,186 +0,0 @@
----
-name: step-reset
-description: Reset database - drop and recreate
-next_step: null
----
-
-# Database Reset
-
-## YOUR TASK:
-
-Completely reset the database: drop, recreate, and apply all migrations.
-
-**WARNING:** This is DESTRUCTIVE. All data will be lost!
-
-**Requires:** `steps/shared/step-00-init.md` completed
-
----
-
-## COMPLIANCE:
-
-| FORBIDDEN | REQUIRED |
-|-----------|----------|
-| `sqlcmd` for DDL/DML | `dotnet ef database drop` |
-| SQL scripts in repo | `dotnet ef database update` |
-| INSERT via scripts | `HasData()` for seeding |
-
-**Exception:** `sqlcmd` allowed ONLY for `BACKUP DATABASE`.
-
----
-
-## EXECUTION SEQUENCE:
-
-### 1. Environment Check
-
-Load validation: `references/database-operations.md#check-required-variables`
-
-```bash
-echo "Reset Configuration"
-echo "==================="
-echo ""
-echo "DbContext:   $DBCONTEXT ($DBCONTEXT_TYPE)"
-echo "Environment: $SELECTED_ENV"
-echo "Database:    $DATABASE_NAME"
-echo "Server:      $SERVER_NAME"
-echo ""
-echo "WARNING: ALL DATA WILL BE LOST!"
-
-# Block production
-block_production
-```
-
-### 2. Confirmation (MANDATORY)
-
-```yaml
-AskUserQuestion:
-  header: "Reset DB"
-  question: "DANGER: Permanently delete '{DATABASE_NAME}'?
-
-ALL DATA WILL BE LOST!
-
-This action is IRREVERSIBLE."
-  options:
-    - label: "Yes, delete {DATABASE_NAME}"
-      description: "Drop + Recreate (IRREVERSIBLE)"
-    - label: "No, cancel"
-      description: "Keep database"
-  multiSelect: false
-```
-
-### 3. Optional Backup
-
-```yaml
-AskUserQuestion:
-  header: "Backup"
-  question: "Backup database before deletion?"
-  options:
-    - label: "Yes, backup (Recommended)"
-      description: "Create .bak via sqlcmd"
-    - label: "No"
-      description: "Dev data only - continue"
-    - label: "Manual backup"
-      description: "Via SSMS/Azure Portal (stops here)"
-  multiSelect: false
-```
-
-**If backup requested:**
-
-Load: `references/database-operations.md#backup-command`
-
-### 4. Drop Database
-
-Load: `references/reset-operations.md#drop-database`
-
-### 5. Recreate + Apply Migrations
-
-Load: `references/reset-operations.md#recreate--apply-migrations`
-
-### 6. Optional Seed
-
-```yaml
-AskUserQuestion:
-  header: "Seed"
-  question: "Populate with test data (HasData)?"
-  options:
-    - label: "Yes (recommended)"
-      description: "Apply HasData configurations"
-    - label: "No"
-      description: "Empty database"
-  multiSelect: false
-```
-
-**If seed requested:**
-
-```bash
-echo ""
-echo "Running seed..."
-
-# HasData is already applied via migrations
-# For custom seeding:
-dotnet run --project "$STARTUP_PROJECT" -- --seed 2>/dev/null || echo "No --seed argument supported"
-```
-
-### 7. Summary
-
-Load: `references/reset-operations.md#summary-after-reset`
-
----
-
-## OUTPUT FORMAT:
-
-```
-RESET COMPLETE
-==============
-Database:    {database_name}
-Environment: {env}
-DbContext:   {dbcontext}
-
-Operations:
-  - Drop: OK
-  - Create: OK
-  - Migrations: {N} applied
-  - Backup: {path | none}
-
-Compliance:  EF Core CLI only
-
-Next: /efcore db-status, /efcore db-seed
-```
-
----
-
-## PROTECTIONS:
-
-Load: `references/troubleshooting.md#reset-protections`
-
----
-
-## BOTH CONTEXTS:
-
-If "Both" selected:
-
-```bash
-# Drop + Recreate CoreDbContext
-DBCONTEXT="CoreDbContext"
-# ... execute reset ...
-
-# Then ExtensionsDbContext
-DBCONTEXT="ExtensionsDbContext"
-# ... execute reset ...
-```
-
----
-
-## OPTIONS:
-
-| Option | Description |
-|--------|-------------|
-| `--env {name}` | Use appsettings.{name}.json |
-| `--no-backup` | Skip backup step |
-| `--context {name}` | Specify DbContext |
-| `--seed` | Auto-seed after reset |
-
----
-
-## COMPLETION:
-
-Database reset complete. Fresh state with all migrations applied.

package/templates/skills/efcore/steps/db/step-seed.md

@@ -1,166 +0,0 @@
----
-name: step-seed
-description: Populate database with test data
-next_step: null
----
-
-# Database Seed
-
-## YOUR TASK:
-
-Populate the database with test or initial data using EF Core conventions.
-
-**Requires:** `steps/shared/step-00-init.md` completed
-
----
-
-## COMPLIANCE:
-
-| FORBIDDEN | REQUIRED |
-|-----------|----------|
-| SQL scripts in repo | `HasData()` in configurations |
-| `sqlcmd` with INSERT | `IDataSeeder` classes |
-| `migrationBuilder.Sql()` INSERT | EF Core typed migrations |
-
----
-
-## EXECUTION SEQUENCE:
-
-### 1. Environment Check
-
-Load validation: `references/database-operations.md#check-required-variables`
-
-```bash
-echo "Seed Configuration"
-echo "=================="
-echo ""
-echo "DbContext:   $DBCONTEXT ($DBCONTEXT_TYPE)"
-echo "Environment: $SELECTED_ENV"
-echo "Database:    $DATABASE_NAME"
-
-# Block production
-block_production
-```
-
-### 2. Detect Available Seed Methods
-
-Load: `references/seed-methods.md#detect-available-seed-methods`
-
-### 3. Select Method
-
-**If multiple methods available:**
-
-```yaml
-AskUserQuestion:
-  header: "Seed"
-  question: "Which seed method to use?"
-  options:
-    - label: "HasData (Recommended)"
-      description: "Via EF Core migrations"
-    - label: "Seeder Class"
-      description: "Run DbSeeder/DataSeeder"
-    - label: "CLI --seed"
-      description: "Launch app with --seed"
-  multiSelect: false
-```
-
-### 4. Execute Seed
-
-Load execution methods from: `references/seed-methods.md#execute-seed-*`
-
-- HasData: `references/seed-methods.md#execute-seed---hasdata`
-- Seeder Class: `references/seed-methods.md#execute-seed---seeder-class`
-- CLI Argument: `references/seed-methods.md#execute-seed---cli-argument`
-
-### 5. Verify (Optional)
-
-Load: `references/seed-methods.md#verify-seed-data`
-
-### 6. Summary
-
-```bash
-echo ""
-echo "==========================================="
-echo "SEED COMPLETE"
-echo "==========================================="
-echo ""
-echo "Database:    $DATABASE_NAME"
-echo "Environment: $SELECTED_ENV"
-echo "Method:      $SEED_METHOD"
-echo ""
-echo "Compliance:  EF Core native, No raw SQL"
-echo ""
-echo "==========================================="
-echo ""
-echo "Next steps:"
-echo "  /efcore db-status    # Check status"
-echo "  dotnet run           # Start application"
-echo ""
-```
-
----
-
-## OUTPUT FORMAT:
-
-```
-SEED COMPLETE
-=============
-Database:    {database_name}
-Environment: {env}
-Method:      {hasdata | seeder-class | cli-argument}
-
-Compliance:  EF Core native, No raw SQL
-
-Next: /efcore db-status, dotnet run
-```
-
----
-
-## NO SEED METHODS FOUND:
-
-Load: `references/troubleshooting.md#seed-setup-guide`
-
----
-
-## MIGRATION FROM SQL:
-
-Load: `references/troubleshooting.md#migration-from-sql`
-
----
-
-## BOTH CONTEXTS:
-
-If `RUN_BOTH=true` (auto-detected for client projects with SmartStack NuGet):
-
-Run the seed sequence for both contexts, in order:
-
-```bash
-# 1. Seed CoreDbContext first (system data: Users, Roles, Permissions...)
-echo "=== Seeding CoreDbContext (core schema) ==="
-DBCONTEXT="CoreDbContext"
-# Run steps 2-6 with CoreDbContext...
-
-# 2. Then ExtensionsDbContext (client data)
-echo ""
-echo "=== Seeding ExtensionsDbContext (extensions schema) ==="
-DBCONTEXT="ExtensionsDbContext"
-# Run steps 2-6 with ExtensionsDbContext...
-```
-
-**Order matters:** Core MUST be seeded first (Extensions may reference Core data via foreign keys).
-
----
-
-## OPTIONS:
-
-| Option | Description |
-|--------|-------------|
-| `--env {name}` | Use appsettings.{name}.json |
-| `--context {name}` | Specify DbContext |
-| `--method {name}` | Force seed method (hasdata, seeder-class, cli-argument) |
-
----
-
-## COMPLETION:
-
-Seed data applied. Use `/efcore db-status` to verify.

package/templates/skills/efcore/steps/db/step-status.md

@@ -1,173 +0,0 @@
----
-name: step-status
-description: Display migrations and database status
-next_step: null
----
-
-# Database Status
-
-## YOUR TASK:
-
-Display comprehensive status of EF Core migrations and database connection.
-
-**Requires:** `steps/shared/step-00-init.md` completed
-
-**Type:** Read-only, no modifications
-
----
-
-## EXECUTION SEQUENCE:
-
-### 0. Validate Required Variables
-
-Load: `references/database-operations.md#check-required-variables`
-
-### 1. Display Configuration
-
-```bash
-echo ""
-echo "EF CORE STATUS"
-echo "=============="
-echo ""
-echo "Project:     $PROJECT_NAME"
-echo "DbContext:   $DBCONTEXT ($DBCONTEXT_TYPE)"
-echo "Schema:      $SCHEMA"
-echo "Environment: $SELECTED_ENV"
-echo "Config:      $CONFIG_FILE"
-```
-
-### 2. Test Database Connection
-
-Load: `references/database-operations.md#connection-test`
-
-### 3. List Migrations
-
-```bash
-echo ""
-echo "Migrations:"
-
-dotnet ef migrations list \
-  --context "$DBCONTEXT" \
-  --project "$INFRA_PROJECT" \
-  --startup-project "$STARTUP_PROJECT"
-```
-
-### 4. Count Applied vs Pending
-
-Load: `references/database-operations.md#migration-count-utilities`
-
-```bash
-echo ""
-echo "Summary:"
-echo "  Total:    $TOTAL migrations"
-echo "  Applied:  $APPLIED"
-echo "  Pending:  $PENDING"
-```
-
-### 5. Check MCP for Conflicts (Optional)
-
-```javascript
-// Call MCP for additional analysis
-const result = await mcp__smartstack__check_migrations({
-  branch: CURRENT_BRANCH
-});
-
-if (result.conflicts && result.conflicts.length > 0) {
-  console.log("");
-  console.log("Conflicts detected:");
-  result.conflicts.forEach(c => console.log("  - " + c));
-}
-```
-
-### 6. Check Naming Compliance
-
-```bash
-echo ""
-echo "Naming compliance:"
-
-# Check migration naming pattern
-PATTERN="^(core|extensions)_v[0-9]+\.[0-9]+\.[0-9]+_[0-9]+_"
-NON_COMPLIANT=$(find "$MIGRATIONS_DIR" -name "*.cs" 2>/dev/null | \
-  grep -v "Designer\|Snapshot" | \
-  xargs -I{} basename {} .cs | \
-  grep -v -E "$PATTERN" | \
-  wc -l)
-
-if [ "$NON_COMPLIANT" -eq 0 ]; then
-  echo "  All migrations follow naming convention"
-else
-  echo "  WARNING: $NON_COMPLIANT migrations have non-standard names"
-fi
-```
-
-### 7. Check 1-Migration-Per-Feature Rule
-
-```bash
-# Count migrations for current branch
-BRANCH_MIGS=$(find "$MIGRATIONS_DIR" -name "*.cs" 2>/dev/null | \
-  grep -v "Designer\|Snapshot" | \
-  xargs -I{} basename {} | \
-  grep -i "$(echo "$CURRENT_BRANCH" | sed 's|.*/||' | tr '-' '_')" | \
-  wc -l)
-
-echo ""
-if [ "$BRANCH_MIGS" -le 1 ]; then
-  echo "1-migration-per-feature: OK"
-else
-  echo "1-migration-per-feature: WARNING ($BRANCH_MIGS migrations for this branch)"
-  echo "  Consider: /efcore squash"
-fi
-```
-
----
-
-## OUTPUT FORMAT:
-
-```
-EF CORE STATUS
-==============
-Project:     {project_name}
-DbContext:   {dbcontext} ({dbcontext_type})
-Schema:      {schema}
-Environment: {env}
-Config:      {config_file}
-
-Connection:  {OK | FAILED}
-
-Migrations:
-  {list of migrations}
-
-Summary:
-  Total:    {N} migrations
-  Applied:  {N}
-  Pending:  {N}
-
-Naming compliance: {OK | WARNING}
-1-migration-per-feature: {OK | WARNING}
-
-{if pending}
-Next: /efcore db-deploy
-{endif}
-```
-
----
-
-## TROUBLESHOOTING (if connection fails):
-
-Load: `references/troubleshooting.md#database-status`
-
----
-
-## OPTIONS:
-
-| Option | Description |
-|--------|-------------|
-| `--verbose` | Show all migrations with details |
-| `--json` | Output as JSON |
-| `--context` | Specify DbContext |
-
----
-
-## COMPLETION:
-
-Status displayed. No modifications made.

package/templates/skills/efcore/steps/migration/step-00-init.md

@@ -1,102 +0,0 @@
----
-name: step-00-init
-description: Initialize migration - cross-branch check and context detection
-next_step: step-01-check.md
----
-
-# Step 0: Initialize Migration
-
-## YOUR TASK:
-
-Detect context, check for cross-branch conflicts, and prepare for migration creation.
-
-**Requires:** `steps/shared/step-00-init.md` completed (provides {dbcontext}, {base_branch}, etc.)
-
----
-
-## RULE:
-
-```
-1 MIGRATION PER FEATURE
-
-- If migration exists for this branch → recreate it
-- Never accumulate multiple migrations per feature
-- Squash before merge if needed
-```
-
----
-
-## EXECUTION SEQUENCE:
-
-### 1. Display Context
-
-```bash
-echo "Migration Context"
-echo "================"
-echo ""
-echo "Branch:     $CURRENT_BRANCH"
-echo "Type:       $BRANCH_TYPE"
-echo "DbContext:  $DBCONTEXT ($DBCONTEXT_TYPE)"
-echo "Schema:     $SCHEMA"
-echo "Migrations: $MIGRATIONS_DIR"
-```
-
-### 2. Cross-Branch Validation (Optional)
-
-```bash
-if [ "$CROSS_BRANCH_ENABLED" = "true" ]; then
-  echo ""
-  echo "Checking cross-branch conflicts..."
-
-  # Get snapshot from develop
-  DEVELOP_SNAPSHOT=$(git show "origin/$BASE_BRANCH:$MIGRATIONS_DIR/${DBCONTEXT}ModelSnapshot.cs" 2>/dev/null || echo "")
-  LOCAL_SNAPSHOT=$(cat "$MIGRATIONS_DIR/${DBCONTEXT}ModelSnapshot.cs" 2>/dev/null || echo "")
-
-  if [ -n "$DEVELOP_SNAPSHOT" ] && [ -n "$LOCAL_SNAPSHOT" ]; then
-    DIFF_LINES=$(diff <(echo "$DEVELOP_SNAPSHOT") <(echo "$LOCAL_SNAPSHOT") 2>/dev/null | wc -l)
-
-    if [ "$DIFF_LINES" -gt 100 ]; then
-      echo ""
-      echo "WARNING: Cross-branch conflict detected ($DIFF_LINES lines differ)"
-      echo "Recommendation: /efcore rebase-snapshot"
-      echo ""
-
-      if [ "$BLOCK_ON_CONFLICT" = "true" ]; then
-        echo "BLOCKED: Use --force to override or rebase first"
-        exit 1
-      fi
-    else
-      echo "  No significant conflicts detected"
-    fi
-  fi
-fi
-```
-
-### 3. Skip If --force Flag
-
-```bash
-if [ "$FORCE_FLAG" = "true" ]; then
-  echo ""
-  echo "Force mode: skipping cross-branch check"
-fi
-```
-
----
-
-## STATE OUTPUT:
-
-| Variable | Description |
-|----------|-------------|
-| `{cross_branch_ok}` | true if no conflicts or force mode |
-| `{diff_lines}` | Number of lines different from parent |
-
----
-
-## SUCCESS CRITERIA:
-
-- DbContext detected
-- Cross-branch check passed (or forced)
-
-## NEXT STEP:
-
-→ `step-01-check.md`