@atlashub/smartstack-cli 4.35.0 → 4.37.0

package/templates/agents/efcore/db-seed.md

@@ -1,73 +0,0 @@
----
-name: efcore-db-seed
-description: EF Core database seed - populate test data
-color: yellow
-model: haiku
-tools: Bash, Glob, Read
----
-
-# EF Core Database Seed Agent
-
-Populates the database with test data.
-
-## FORBIDDEN
-
-- **NEVER** create, delete, modify, or recreate migrations (`dotnet ef migrations add/remove` is FORBIDDEN)
-- **NEVER** drop or recreate the database (`dotnet ef database drop` is FORBIDDEN)
-- This agent ONLY seeds data into an existing database
-
-## WSL Preflight (MANDATORY - run BEFORE any git command)
-
-```bash
-# Repair worktree .git file if Windows path detected under WSL
-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 "Worktree .git path repaired for WSL"
-fi
-```
-
-## Workflow
-
-1. **Detect** available seeding method:
-   - SQL Script: `scripts/seed.sql`
-   - HasData: in configurations
-   - CLI: `--seed` argument
-2. **Execute** the found method
-3. **Verify** insertion
-
-## Detection
-
-```bash
-# SQL Script
-test -f scripts/seed.sql && echo "sql-script"
-
-# HasData
-grep -r "\.HasData(" --include="*.cs" && echo "hasdata"
-
-# CLI seed
-grep -q "\-\-seed" Program.cs && echo "cli-seed"
-```
-
-## Execution
-
-```bash
-# SQL Script
-sqlcmd -S $SERVER -E -d $DATABASE -i scripts/seed.sql
-
-# CLI
-dotnet run -- --seed
-```
-
-## Output Format
-
-```
-DB SEED
-  Method: {sql-script|hasdata|cli}
-  Status: {success|error}
-  Records: {n} inserted (if available)
-```
-
-## Priority
-
-Speed > Detail. Execute without too many questions.

package/templates/agents/efcore/db-status.md

@@ -1,97 +0,0 @@
----
-name: efcore-db-status
-description: EF Core database status - fast migration state check
-color: blue
-model: haiku
-tools: Bash, Glob
----
-
-# EF Core Database Status Agent
-
-Fast check of EF Core migration state using **SmartStack MCP**.
-
-## FORBIDDEN
-
-- **NEVER** create, delete, modify, or recreate migrations
-- **NEVER** modify the database (`dotnet ef database update/drop` is FORBIDDEN)
-- This agent is READ-ONLY: it only checks status, never modifies anything
-
-## WSL Preflight (MANDATORY - run BEFORE any git command)
-
-```bash
-# Repair worktree .git file if Windows path detected under WSL
-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 "Worktree .git path repaired for WSL"
-fi
-```
-
-## Workflow
-
-1. **Invoke MCP** for migration list and naming validation
-2. **Test** DB connection with `dotnet ef`
-3. **Count** applied vs pending
-4. **Verify** 1 migration per feature rule
-5. **Output** compact summary
-
-## MCP Integration
-
-**Primary method:** Get structured migration data
-
-```
-CALL mcp__smartstack__check_migrations WITH:
-  - branch: {current_branch}
-```
-
-**Response fields used:**
-- `migrations[]` - List with name, context, version, sequence
-- `conflicts[]` - Any naming issues
-
-## Fallback Commands (if MCP unavailable)
-
-```bash
-# Migrations
-dotnet ef migrations list --no-build 2>/dev/null | grep -v "^Build"
-
-# Branch
-git branch --show-current
-```
-
-## Output Format
-
-```
-================================================================================
-                         EF CORE - DATABASE STATUS
-================================================================================
-
-CORE CONTEXT (CoreDbContext)
-  Schema: core
-  History: core.__EFMigrationsHistory
-  Migrations: {applied}/{total} | {pending} pending
-
-EXTENSIONS CONTEXT (ExtensionsDbContext)
-  Schema: extensions
-  History: extensions.__EFMigrationsHistory
-  Migrations: {applied}/{total} | {pending} pending
-
-BRANCH STATUS
-  Branch: {branch}
-  Core migrations: {n}
-  Extensions migrations: {n}
-  Naming: {ok|warnings}
-  1-migration rule: {ok|warning}
-
-================================================================================
-```
-
-## Dual DbContext Notes
-
-- **Core migrations** use `--context CoreDbContext`
-- **Extensions migrations** use `--context ExtensionsDbContext`
-- Each context has its own `__EFMigrationsHistory` table
-- Check both contexts when verifying migration status
-
-## Priority
-
-Speed > Detail. Use MCP for structured data, dotnet ef for connection test.

package/templates/agents/efcore/scan.md

@@ -1,124 +0,0 @@
----
-name: efcore-scan
-description: EF Core cross-branch migration scanner - detect conflicts before they happen
-color: cyan
-model: haiku
-tools: Bash, Glob, Read
----
-
-# EF Core Scan Agent
-
-Cross-branch scanner using **SmartStack MCP** to detect migrations across all active branches.
-
-## WSL Preflight (MANDATORY - run BEFORE any git command)
-
-```bash
-# Repair worktree .git file if Windows path detected under WSL
-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 "Worktree .git path repaired for WSL"
-fi
-```
-
-## Mission
-
-1. **List** all active worktrees
-2. **Invoke MCP** for each branch
-3. **Aggregate** results into summary
-4. **Analyze** conflict risks
-5. **Recommend** optimal merge order
-
-## Base Branch Determination
-
-**BEFORE calling MCP, determine the correct base branch for each worktree:**
-
-```bash
-# For each branch, determine its base:
-#   feature/*  → compareBranch: "develop"
-#   release/*  → compareBranch: "main"
-#   hotfix/*   → compareBranch: "main"
-#   develop    → compareBranch: "main"
-determine_compare_branch() {
-  case "$1" in
-    feature/*)  echo "develop" ;;
-    release/*)  echo "main" ;;
-    hotfix/*)   echo "main" ;;
-    develop)    echo "main" ;;
-    *)          echo "develop" ;;
-  esac
-}
-```
-
-## MCP Integration
-
-**Primary method:** Loop through branches and call MCP with the **correct base branch**
-
-```
-FOR each branch in active_worktrees:
-  COMPARE_BRANCH = determine_compare_branch(branch)
-  CALL mcp__smartstack__check_migrations WITH:
-    - branch: {branch}
-    - compareBranch: {COMPARE_BRANCH}
-  STORE result
-```
-
-**Response structure:**
-
-```typescript
-{
-  hasConflicts: boolean;
-  migrations: MigrationInfo[];
-  conflicts: MigrationConflict[];
-  suggestions: string[];
-}
-```
-
-## Fallback Commands (if MCP unavailable)
-
-```bash
-# List worktrees (run preflight_git_check first for cross-platform compatibility)
-detect_platform
-repair_worktree_paths "$(git rev-parse --git-common-dir 2>/dev/null || echo '.bare')"
-git worktree list
-
-# ModelSnapshot hash
-md5sum Migrations/*ModelSnapshot.cs | cut -d' ' -f1
-
-# Compare with develop
-diff -q local/Snapshot.cs develop/Snapshot.cs
-
-# Count migrations
-find Migrations -name "*.cs" | grep -v Designer | grep -v Snapshot | wc -l
-```
-
-## Risk Levels
-
-| MCP Conflict Type | Level | Action |
-|-------------------|-------|--------|
-| (none) | NONE | Direct merge OK |
-| `naming` | LOW | Merge OK |
-| `order` | MEDIUM | Attention to order |
-| `dependency` | HIGH | Rebase required |
-| `snapshot` | CRITICAL | Manual intervention |
-
-## Output Format
-
-```
-================================================================================
-                    EF CORE CROSS-BRANCH SCAN (via MCP)
-================================================================================
-
-BRANCHES (n)
-  {branch} | {migrations.length} | Risk: {level}
-
-RECOMMENDED MERGE ORDER
-  1. {branch} (reason)
-  2. {branch} (reason)
-
-================================================================================
-```
-
-## Priority
-
-Speed > Accuracy. Read-only, no modifications.

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

@@ -1,32 +0,0 @@
-# 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/destructive-operations.md

@@ -1,38 +0,0 @@
-# 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.

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

@@ -1,217 +0,0 @@
----
-name: step-deploy
-description: Deploy pending migrations to database
-next_step: null
----
-
-# Database Deploy
-
-## YOUR TASK:
-
-Apply pending EF Core migrations to the local database.
-
-**Requires:** `steps/shared/step-00-init.md` completed
-
----
-
-## EXECUTION SEQUENCE:
-
-### 1. Environment Check
-
-```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
-
-echo "Deploy Configuration"
-echo "===================="
-echo ""
-echo "DbContext:   $DBCONTEXT ($DBCONTEXT_TYPE)"
-echo "Environment: $SELECTED_ENV"
-echo "Database:    $DATABASE_NAME"
-echo "Server:      $SERVER_NAME"
-
-# Block production
-block_production
-```
-
-### 2. Check Pending Migrations
-
-```bash
-echo ""
-echo "Checking pending migrations..."
-
-EF_STDERR=$(mktemp)
-PENDING=$(dotnet ef migrations list \
-  --context "$DBCONTEXT" \
-  --project "$INFRA_PROJECT" \
-  --startup-project "$STARTUP_PROJECT" 2>"$EF_STDERR" | \
-  grep -c "(Pending)" || echo "0")
-
-# Check for real errors (not just build output)
-if grep -qi "error\|exception\|failed" "$EF_STDERR" 2>/dev/null; then
-  echo "WARNING: EF Core reported errors:"
-  grep -i "error\|exception\|failed" "$EF_STDERR" | head -5
-fi
-rm -f "$EF_STDERR"
-
-echo "Pending: $PENDING migration(s)"
-
-if [ "$PENDING" -eq 0 ]; then
-  echo ""
-  echo "No pending migrations. Database is up to date."
-  echo ""
-  echo "Next steps:"
-  echo "  /efcore migration    # Create new migration"
-  echo "  /efcore db-status    # Check status"
-  exit 0
-fi
-```
-
-### 3. List Pending Migrations
-
-```bash
-echo ""
-echo "Migrations to apply:"
-
-dotnet ef migrations list \
-  --context "$DBCONTEXT" \
-  --project "$INFRA_PROJECT" \
-  --startup-project "$STARTUP_PROJECT" 2>/dev/null | \
-  grep "(Pending)" | while read line; do
-    echo "  - $line"
-  done
-```
-
-### 4. Confirmation (if not auto mode)
-
-```yaml
-AskUserQuestion:
-  header: "Deploy"
-  question: "Apply {PENDING} migration(s) to {DATABASE_NAME}?"
-  options:
-    - label: "Yes, apply"
-      description: "Deploy to {SELECTED_ENV} environment"
-    - label: "Cancel"
-      description: "Do not apply"
-  multiSelect: false
-```
-
-### 5. Apply Migrations
-
-```bash
-echo ""
-echo "Applying migrations..."
-echo ""
-
-dotnet ef database update \
-  --context "$DBCONTEXT" \
-  --project "$INFRA_PROJECT" \
-  --startup-project "$STARTUP_PROJECT" \
-  --verbose
-EXIT_CODE=$?
-
-if [ $EXIT_CODE -ne 0 ]; then
-  echo ""
-  echo "ERROR: Migration failed (exit code: $EXIT_CODE)"
-  echo ""
-  echo "Troubleshooting:"
-  echo "  - Check database connection"
-  echo "  - Review migration content"
-  echo "  - Try: /efcore db-reset"
-  exit 1
-fi
-```
-
-### 6. Verify
-
-```bash
-echo ""
-echo "Verifying..."
-
-NEW_PENDING=$(dotnet ef migrations list \
-  --context "$DBCONTEXT" \
-  --project "$INFRA_PROJECT" \
-  --startup-project "$STARTUP_PROJECT" 2>/dev/null | \
-  grep -c "(Pending)" || echo "0")
-
-if [ "$NEW_PENDING" -eq 0 ]; then
-  echo "All migrations applied successfully."
-else
-  echo "WARNING: $NEW_PENDING migrations still pending"
-fi
-```
-
-### 7. Summary
-
-```bash
-echo ""
-echo "==========================================="
-echo "DEPLOY COMPLETE"
-echo "==========================================="
-echo ""
-echo "Database:    $DATABASE_NAME"
-echo "Environment: $SELECTED_ENV"
-echo "DbContext:   $DBCONTEXT"
-echo "Applied:     $PENDING migration(s)"
-echo ""
-echo "==========================================="
-echo ""
-echo "Next steps:"
-echo "  /efcore db-status    # Verify status"
-echo "  /efcore db-seed      # Add test data"
-echo ""
-```
-
----
-
-## OUTPUT FORMAT:
-
-```
-DEPLOY COMPLETE
-===============
-Database:    {database_name}
-Environment: {env}
-DbContext:   {dbcontext}
-Applied:     {N} migration(s)
-
-Next: /efcore db-status, /efcore db-seed
-```
-
----
-
-## ERROR HANDLING:
-
-| Error | Resolution |
-|-------|------------|
-| Connection failed | Check SQL Server, credentials |
-| Migration error | Review migration, consider reset |
-| Constraint violation | Check data, may need seed |
-
----
-
-## OPTIONS:
-
-| Option | Description |
-|--------|-------------|
-| `--env {name}` | Use appsettings.{name}.json |
-| `--verbose` | Show SQL statements |
-| `--context {name}` | Specify DbContext |
-
----
-
-## BOTH CONTEXTS:
-
-Load: `references/both-contexts.md`
-
----
-
-## COMPLETION:
-
-Migrations applied. Use `/efcore db-status` to verify.