@atlashub/smartstack-cli 3.39.0 → 3.41.0

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

@@ -1,166 +1,166 @@
----
-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.
+---
+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 +1,173 @@
----
-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.
+---
+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.