@atlashub/smartstack-cli 3.41.0 → 3.42.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@atlashub/smartstack-cli",
-  "version": "3.41.0",
+  "version": "3.42.0",
   "description": "SmartStack Claude Code automation toolkit - GitFlow, EF Core migrations, prompts and more",
   "author": {
     "name": "SmartStack",

package/templates/agents/efcore/conflicts.md

@@ -2,9 +2,8 @@
 name: efcore-conflicts
 description: EF Core conflict analyzer - BLOCKING if conflict detected
 color: red
-model: sonnet
+model: haiku
 tools: Bash, Glob, Read
-mcp: mcp__smartstack__check_migrations
 ---
 
 # EF Core Conflicts Agent

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

@@ -2,11 +2,8 @@
 name: efcore-db-deploy
 description: EF Core database deploy - apply pending migrations
 color: green
-model: sonnet
+model: haiku
 tools: Bash, Glob
-steps:
-  - steps/shared/step-00-init.md
-  - steps/db/step-deploy.md
 ---
 
 # EF Core Database Deploy Agent

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

@@ -2,11 +2,8 @@
 name: efcore-db-reset
 description: EF Core database reset - drop and recreate (DESTRUCTIVE)
 color: red
-model: sonnet
+model: haiku
 tools: Bash, Glob, Read
-steps:
-  - steps/shared/step-00-init.md
-  - steps/db/step-reset.md
 ---
 
 # EF Core Database Reset Agent

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

@@ -4,9 +4,6 @@ description: EF Core database seed - populate test data
 color: yellow
 model: haiku
 tools: Bash, Glob, Read
-steps:
-  - steps/shared/step-00-init.md
-  - steps/db/step-seed.md
 ---
 
 # EF Core Database Seed Agent

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

@@ -4,10 +4,6 @@ description: EF Core database status - fast migration state check
 color: blue
 model: haiku
 tools: Bash, Glob
-mcp: mcp__smartstack__check_migrations
-steps:
-  - steps/shared/step-00-init.md
-  - steps/db/step-status.md
 ---
 
 # EF Core Database Status Agent

package/templates/agents/efcore/migration.md

@@ -4,12 +4,6 @@ description: EF Core migration manager - orchestrates MCP for naming (1 per feat
 color: magenta
 model: sonnet
 tools: Bash, Glob, Read, Edit
-steps:
-  - steps/shared/step-00-init.md
-  - steps/migration/step-00-init.md
-  - steps/migration/step-01-check.md
-  - steps/migration/step-02-create.md
-  - steps/migration/step-03-validate.md
 ---
 
 # EF Core Migration Agent

package/templates/agents/efcore/rebase-snapshot.md

@@ -4,13 +4,6 @@ description: EF Core snapshot rebaser - resync ModelSnapshot with develop
 color: yellow
 model: sonnet
 tools: Bash, Glob, Read, Edit
-steps:
-  - steps/shared/step-00-init.md
-  - steps/rebase-snapshot/step-00-init.md
-  - steps/rebase-snapshot/step-01-backup.md
-  - steps/rebase-snapshot/step-02-fetch.md
-  - steps/rebase-snapshot/step-03-create.md
-  - steps/rebase-snapshot/step-04-validate.md
 ---
 
 # EF Core Rebase-Snapshot Agent

package/templates/agents/efcore/scan.md

@@ -2,9 +2,8 @@
 name: efcore-scan
 description: EF Core cross-branch migration scanner - detect conflicts before they happen
 color: cyan
-model: sonnet
+model: haiku
 tools: Bash, Glob, Read
-mcp: mcp__smartstack__check_migrations
 ---
 
 # EF Core Scan Agent

package/templates/agents/efcore/squash.md

@@ -4,13 +4,6 @@ description: EF Core migration squasher - combine multiple migrations into one
 color: magenta
 model: sonnet
 tools: Bash, Glob, Read
-steps:
-  - steps/shared/step-00-init.md
-  - steps/squash/step-00-init.md
-  - steps/squash/step-01-backup.md
-  - steps/squash/step-02-fetch.md
-  - steps/squash/step-03-create.md
-  - steps/squash/step-04-validate.md
 ---
 
 # EF Core Squash Agent

package/templates/skills/efcore/SKILL.md

@@ -8,10 +8,9 @@ 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.
+Manage EF Core migrations and database operations. **ALWAYS delegate to Task agents** for fast execution.
 </objective>
 
 <quick_start>
@@ -33,88 +32,48 @@ Manage EF Core migrations and database operations with progressive step loading,
 ```
 </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:**
+**ROUTING: ALWAYS delegate to Task agent. Never execute inline.**
 
-1. Parse command and flags from input
-2. Load shared init step: `steps/shared/step-00-init.md`
-3. Route to command-specific steps:
+Parse the command from `$ARGUMENTS` and delegate to the matching agent:
 
-| 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) |
+| Command | Task Agent (`subagent_type`) | Model | Description |
+|---------|----------------------------|-------|-------------|
+| `db-status` | `efcore-db-status` | haiku | Fast migration state check |
+| `db-deploy` | `efcore-db-deploy` | haiku | Apply pending migrations |
+| `db-reset` | `efcore-db-reset` | haiku | Drop + recreate database |
+| `db-seed` | `efcore-db-seed` | haiku | Populate with test data |
+| `migration` | `efcore-migration` | sonnet | Create/recreate migration (MCP) |
+| `squash` | `efcore-squash` | sonnet | Consolidate migrations (MCP) |
+| `rebase-snapshot` | `efcore-rebase-snapshot` | sonnet | Sync snapshot with parent (MCP) |
+| `scan` | `efcore-scan` | haiku | Cross-branch conflict scan |
+| `conflicts` | `efcore-conflicts` | haiku | Conflict analysis |
 
-</entry_point>
+**Delegation template:**
 
-<shared_functions>
-**Always load first:** `steps/shared/step-00-init.md`
+```
+Task(
+  subagent_type: "{agent_name}",
+  prompt: "Execute /efcore {command} in {cwd}. Branch: {branch}. Flags: {flags}",
+  mode: "bypassPermissions"
+)
+```
 
-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
+**Pass to agent prompt:**
+- Current working directory (absolute path)
+- Current branch name
+- Any flags (--context, --force)
+- User's description (for migration command)
 
-**MCP Integration:**
-- `mcp__smartstack__suggest_migration` - Generate compliant names
-- `mcp__smartstack__check_migrations` - Analyze conflicts
-- `mcp__smartstack__validate_conventions` - Validate structure
-</shared_functions>
+</entry_point>
 
 <dual_dbcontext>
 SmartStack uses **two separate DbContexts**:
@@ -123,12 +82,6 @@ SmartStack uses **two separate DbContexts**:
 |---------|-----------|--------|---------------|
 | `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>
@@ -136,33 +89,12 @@ SmartStack uses **two separate DbContexts**:
 
 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.
+**FORBIDDEN:** Manual name calculation. Always use `mcp__smartstack__suggest_migration`.
 </naming_convention>
 
 <safety_rules>
-1. **Backup MANDATORY** for destructive operations
+1. **Backup MANDATORY** for destructive operations (db-reset, squash)
 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
+4. **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>