@atlashub/smartstack-cli 4.35.0 → 4.36.0

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`

package/templates/skills/efcore/steps/migration/step-01-check.md

@@ -1,164 +0,0 @@
----
-name: step-01-check
-description: Check for existing migration and decide action
-next_step: step-02-create.md
----
-
-# Step 1: Check Existing Migration
-
-## YOUR TASK:
-
-Search for existing migrations for this branch and decide whether to recreate or skip.
-
-**Previous step:** `step-00-init.md`
-
----
-
-## EXECUTION SEQUENCE:
-
-### 0. Validate Required Variables
-
-```bash
-# Validate required variables from step-00-init
-for VAR_NAME in DBCONTEXT DBCONTEXT_TYPE MIGRATIONS_DIR INFRA_PROJECT STARTUP_PROJECT CURRENT_BRANCH BRANCH_TYPE; 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
-```
-
-### 1. Build Search Pattern
-
-```bash
-# Extract branch name for pattern
-case "$BRANCH_TYPE" in
-  feature)
-    BRANCH_SHORT=$(echo "$CURRENT_BRANCH" | sed 's|feature/||' | tr '-' '_')
-    ;;
-  release)
-    BRANCH_SHORT=$(echo "$CURRENT_BRANCH" | sed 's|release/||' | tr '.' '_')
-    ;;
-  hotfix)
-    BRANCH_SHORT=$(echo "$CURRENT_BRANCH" | sed 's|hotfix/||' | tr '.' '_')
-    ;;
-  *)
-    BRANCH_SHORT=""
-    ;;
-esac
-
-echo "Searching for existing migrations..."
-echo "  Pattern: *${BRANCH_SHORT}*"
-```
-
-### 2. Find Existing Migrations
-
-```bash
-# Sanitize branch name: only allow alphanumeric, underscore (prevent regex/shell injection)
-BRANCH_SHORT_SAFE=$(echo "$BRANCH_SHORT" | sed 's/[^a-zA-Z0-9_]//g')
-if [ -z "$BRANCH_SHORT_SAFE" ]; then
-  echo "ERROR: Invalid branch name (no alphanumeric characters after sanitization)"
-  exit 1
-fi
-
-# Search for migrations matching this branch (-F = fixed-string, prevents regex injection)
-EXISTING_MIGRATIONS=$(find "$MIGRATIONS_DIR" -name "*.cs" ! -name "*Designer.cs" ! -name "*Snapshot.cs" -type f 2>/dev/null | \
-  xargs -I{} basename {} | \
-  grep -iF "$BRANCH_SHORT_SAFE" || echo "")
-
-EXISTING_COUNT=$(echo "$EXISTING_MIGRATIONS" | grep -c "^[^ ]" 2>/dev/null || echo "0")
-
-echo ""
-if [ "$EXISTING_COUNT" -gt 0 ]; then
-  echo "Found $EXISTING_COUNT existing migration(s):"
-  echo "$EXISTING_MIGRATIONS" | while read mig; do
-    echo "  - $mig"
-  done
-else
-  echo "No existing migration for this branch."
-fi
-```
-
-### 3. Decide Action
-
-**If migrations exist and NOT force mode:**
-
-```yaml
-AskUserQuestion:
-  header: "Migration"
-  question: "Found {EXISTING_COUNT} existing migration(s). What do you want to do?"
-  options:
-    - label: "Recreate (Recommended)"
-      description: "Delete existing and create new"
-    - label: "Keep and add new"
-      description: "Add another migration (not recommended)"
-    - label: "Cancel"
-      description: "Do nothing"
-  multiSelect: false
-```
-
-**Handle response:**
-
-```javascript
-if (answer === "Recreate (Recommended)" || force_mode) {
-  // Delete existing migrations
-  ACTION = "recreate";
-} else if (answer === "Keep and add new") {
-  ACTION = "add";
-  // Warning: violates 1-migration-per-feature rule
-} else {
-  // Cancel
-  exit(0);
-}
-```
-
-### 4. Delete Existing (If Recreate)
-
-```bash
-if [ "$ACTION" = "recreate" ]; then
-  echo ""
-  echo "Removing existing migrations..."
-
-  for mig in $EXISTING_MIGRATIONS; do
-    mig_name="${mig%.cs}"
-
-    rm -f "$MIGRATIONS_DIR/${mig_name}.cs"
-    rm -f "$MIGRATIONS_DIR/${mig_name}.Designer.cs"
-
-    # Verify deletion succeeded
-    if [ -f "$MIGRATIONS_DIR/${mig_name}.cs" ]; then
-      echo "  ERROR: Failed to delete ${mig_name}.cs"
-      exit 1
-    fi
-
-    echo "  Removed: $mig_name"
-  done
-
-  echo ""
-  echo "Existing migrations removed."
-fi
-```
-
----
-
-## STATE OUTPUT:
-
-| Variable | Description |
-|----------|-------------|
-| `{existing_migrations}` | List of existing migrations |
-| `{existing_count}` | Number found |
-| `{action}` | "recreate", "add", or "cancel" |
-
----
-
-## SUCCESS CRITERIA:
-
-- Existing migrations identified
-- User decision captured
-- Old migrations removed (if recreate)
-
-## NEXT STEP:
-
-→ `step-02-create.md`