@atlashub/smartstack-cli 1.5.1 → 1.5.3

package/templates/commands/efcore.md

@@ -1,224 +1,224 @@
----
-description: EF Core Commands - Migration and database management
----
-
-# EF Core Commands
-
-Set of commands to manage Entity Framework Core: migrations, database, and seeding.
-
-> **MCP INTEGRATION:** Commands use `mcp__smartstack__check_migrations` for conflict analysis and validation.
-
-## Available Commands
-
-### Migrations
-
-| Command | Description | Risk |
-|---------|-------------|------|
-| `/efcore:migration` | Create/recreate migration (1 per feature) | Low |
-| `/efcore:db-status` | Show migration status | None (read-only) |
-| `/efcore:db-deploy` | Apply migrations | Low |
-| `/efcore:db-seed` | Populate with data | Low |
-| `/efcore:db-reset` | Drop + Recreate database | **HIGH** |
-
-### Cross-Branch (v1.2)
-
-| Command | Description | Risk |
-|---------|-------------|------|
-| `/efcore:scan` | Scan migrations across all branches | None (read-only) |
-| `/efcore:conflicts` | Analyze potential conflicts (BLOCKING) | None (read-only) |
-| `/efcore:rebase-snapshot` | Rebase ModelSnapshot on develop | Medium |
-| `/efcore:squash` | Merge multiple migrations into one | **HIGH** |
-
-## Golden Rule: 1 Migration per Feature
-
-**Never accumulate multiple migrations on a feature.** If you modify the model:
-1. Delete the existing migration
-2. Recreate it with `/efcore:migration`
-
-The `/efcore:migration` command handles this automatically.
-
-## Migration Naming
-
-Pattern: `{context}_v{version}_{sequence}_{Description}` (aligned with SmartStack MCP)
-
-| Context | Version | Sequence | Description | Generated Name |
-|---------|---------|----------|-------------|----------------|
-| core | 1.2.0 | 001 | AddUserRoles | `core_v1.2.0_001_AddUserRoles` |
-| core | 1.2.0 | 002 | AddPermissions | `core_v1.2.0_002_AddPermissions` |
-| extensions | 1.3.0 | 001 | AddCustomFields | `extensions_v1.3.0_001_AddCustomFields` |
-
-> **Note:** Context is `core` for SmartStack platform tables, `extensions` for client-specific extensions.
-
-## Typical Workflow
-
-```
-1. /gitflow:10-start feature xxx    → Create worktree + appsettings.Local.json
-2. /efcore:db-deploy                → Apply existing migrations
-3. ... model modifications ...
-4. /efcore:migration                → Create THE migration for this feature
-5. /efcore:db-deploy                → Apply to local DB
-6. /gitflow:3-commit                → Commit
-```
-
-## Cross-Branch Workflow (v1.2)
-
-With GitFlow worktrees, multiple branches can have migrations in parallel. To avoid conflicts:
-
-```
-1. /efcore:scan                → Scan all active branches
-2. /efcore:conflicts           → Check for conflicts (BLOCKING)
-3. /efcore:rebase-snapshot     → If conflict, rebase on develop
-4. /efcore:migration           → Create/recreate migration
-```
-
-### Recommended Merge Order
-
-The scan analyzes migrations and recommends a merge order:
-
-```
-ACTIVE BRANCHES (3)
---------------------
-feature/user-roles    +1 migration    Conflict: NONE
-feature/add-products  +1 migration    Conflict: POTENTIAL
-feature/orders        +2 migrations   Conflict: HIGH
-
-RECOMMENDED MERGE ORDER:
-1. feature/user-roles (independent)
-2. feature/add-products (before orders)
-3. feature/orders (rebase required)
-```
-
-## Configuration
-
-Commands use configuration in `.claude/gitflow/config.json`:
-
-```json
-{
-  "efcore": {
-    "database": {
-      "configFile": "appsettings.Local.json",
-      "connectionStringName": "DefaultConnection",
-      "provider": "SqlServer"
-    },
-    "crossBranch": {
-      "enabled": true,
-      "scanOnMigrationCreate": true,
-      "blockOnConflict": true,
-      "cacheExpiry": 300
-    }
-  }
-}
-```
-
-### crossBranch Options
-
-| Option | Description | Default |
-|--------|-------------|---------|
-| `enabled` | Enable cross-branch validation | `true` |
-| `scanOnMigrationCreate` | Scan before `/efcore:migration` | `true` |
-| `blockOnConflict` | Block if conflict detected | `true` |
-| `cacheExpiry` | Scan cache duration (seconds) | `300` |
-
-## Environment Selection (NEW)
-
-All EF Core commands now display the target database BEFORE execution:
-
-```
-================================================================================
-                         EF CORE - DATABASE DEPLOY
-================================================================================
-
-FICHIERS DISPONIBLES:
-  - appsettings.json
-  - appsettings.Local.json
-  - appsettings.Development.json
-
-ENVIRONNEMENT: appsettings.Local.json
-
-CONNEXION CIBLE:
-  Server:   localhost
-  Database: SmartStack_Dev
-  String:   Server=localhost;Database=SmartStack_Dev;...
-
-================================================================================
-```
-
-### Override Environment
-
-Use `--env` flag to target a different environment:
-
-```bash
-# Deploy to Development environment
-/efcore:db-deploy --env Development
-
-# Reset Staging database
-/efcore:db-reset --env Staging
-```
-
-### Protection Production
-
-Commands that modify the database are **automatically blocked** if `appsettings.Production.json` is detected.
-
-## appsettings.Local.json File
-
-This file contains the local connection string and is **never committed**:
-
-```json
-{
-  "ConnectionStrings": {
-    "DefaultConnection": "Server=localhost;Database=MyApp;Trusted_Connection=true;TrustServerCertificate=true"
-  }
-}
-```
-
-The file is automatically created by `/gitflow:10-start` and added to `.gitignore`.
-
-## Prerequisites
-
-- .NET SDK installed
-- EF Core Tools: `dotnet tool install --global dotnet-ef`
-- SQL Server (or other configured provider)
-
----
-
-## MCP Integration
-
-The following commands use **SmartStack MCP** for enhanced functionality:
-
-| Command | MCP Tool | Purpose |
-|---------|----------|---------|
-| `/efcore:db-status` | `check_migrations` | Get structured migration list |
-| `/efcore:conflicts` | `check_migrations` | Analyze branch conflicts |
-| `/efcore:scan` | `check_migrations` | Multi-branch analysis |
-
-### MCP Tool Reference
-
-**Tool:** `mcp__smartstack__check_migrations`
-
-**Description:** Analyze EF Core migrations for conflicts, ordering issues, and ModelSnapshot discrepancies between branches.
-
-**Parameters:**
-
-| Parameter | Type | Description |
-|-----------|------|-------------|
-| `projectPath` | string | EF Core project path (default: auto-detect) |
-| `branch` | string | Git branch to check (default: current) |
-| `compareBranch` | string | Branch to compare against |
-
-**Response:** `MigrationCheckResult`
-
-```typescript
-interface MigrationCheckResult {
-  hasConflicts: boolean;
-  migrations: MigrationInfo[];
-  conflicts: MigrationConflict[];
-  suggestions: string[];
-}
-```
-
-### Benefits of MCP Integration
-
-1. **Consistency:** Same analysis logic in CLI, CI/CD, and IDE
-2. **Structured Data:** Typed responses instead of text parsing
-3. **Single Source of Truth:** Convention rules in MCP config
-4. **Extensibility:** New checks benefit all commands
+---
+description: EF Core Commands - Migration and database management
+---
+
+# EF Core Commands
+
+Set of commands to manage Entity Framework Core: migrations, database, and seeding.
+
+> **MCP INTEGRATION:** Commands use `mcp__smartstack__check_migrations` for conflict analysis and validation.
+
+## Available Commands
+
+### Migrations
+
+| Command | Description | Risk |
+|---------|-------------|------|
+| `/efcore:migration` | Create/recreate migration (1 per feature) | Low |
+| `/efcore:db-status` | Show migration status | None (read-only) |
+| `/efcore:db-deploy` | Apply migrations | Low |
+| `/efcore:db-seed` | Populate with data | Low |
+| `/efcore:db-reset` | Drop + Recreate database | **HIGH** |
+
+### Cross-Branch (v1.2)
+
+| Command | Description | Risk |
+|---------|-------------|------|
+| `/efcore:scan` | Scan migrations across all branches | None (read-only) |
+| `/efcore:conflicts` | Analyze potential conflicts (BLOCKING) | None (read-only) |
+| `/efcore:rebase-snapshot` | Rebase ModelSnapshot on develop | Medium |
+| `/efcore:squash` | Merge multiple migrations into one | **HIGH** |
+
+## Golden Rule: 1 Migration per Feature
+
+**Never accumulate multiple migrations on a feature.** If you modify the model:
+1. Delete the existing migration
+2. Recreate it with `/efcore:migration`
+
+The `/efcore:migration` command handles this automatically.
+
+## Migration Naming
+
+Pattern: `{context}_v{version}_{sequence}_{Description}` (aligned with SmartStack MCP)
+
+| Context | Version | Sequence | Description | Generated Name |
+|---------|---------|----------|-------------|----------------|
+| core | 1.2.0 | 001 | AddUserRoles | `core_v1.2.0_001_AddUserRoles` |
+| core | 1.2.0 | 002 | AddPermissions | `core_v1.2.0_002_AddPermissions` |
+| extensions | 1.3.0 | 001 | AddCustomFields | `extensions_v1.3.0_001_AddCustomFields` |
+
+> **Note:** Context is `core` for SmartStack platform tables, `extensions` for client-specific extensions.
+
+## Typical Workflow
+
+```
+1. /gitflow:10-start feature xxx    → Create worktree + appsettings.Local.json
+2. /efcore:db-deploy                → Apply existing migrations
+3. ... model modifications ...
+4. /efcore:migration                → Create THE migration for this feature
+5. /efcore:db-deploy                → Apply to local DB
+6. /gitflow:3-commit                → Commit
+```
+
+## Cross-Branch Workflow (v1.2)
+
+With GitFlow worktrees, multiple branches can have migrations in parallel. To avoid conflicts:
+
+```
+1. /efcore:scan                → Scan all active branches
+2. /efcore:conflicts           → Check for conflicts (BLOCKING)
+3. /efcore:rebase-snapshot     → If conflict, rebase on develop
+4. /efcore:migration           → Create/recreate migration
+```
+
+### Recommended Merge Order
+
+The scan analyzes migrations and recommends a merge order:
+
+```
+ACTIVE BRANCHES (3)
+--------------------
+feature/user-roles    +1 migration    Conflict: NONE
+feature/add-products  +1 migration    Conflict: POTENTIAL
+feature/orders        +2 migrations   Conflict: HIGH
+
+RECOMMENDED MERGE ORDER:
+1. feature/user-roles (independent)
+2. feature/add-products (before orders)
+3. feature/orders (rebase required)
+```
+
+## Configuration
+
+Commands use configuration in `.claude/gitflow/config.json`:
+
+```json
+{
+  "efcore": {
+    "database": {
+      "configFile": "appsettings.Local.json",
+      "connectionStringName": "DefaultConnection",
+      "provider": "SqlServer"
+    },
+    "crossBranch": {
+      "enabled": true,
+      "scanOnMigrationCreate": true,
+      "blockOnConflict": true,
+      "cacheExpiry": 300
+    }
+  }
+}
+```
+
+### crossBranch Options
+
+| Option | Description | Default |
+|--------|-------------|---------|
+| `enabled` | Enable cross-branch validation | `true` |
+| `scanOnMigrationCreate` | Scan before `/efcore:migration` | `true` |
+| `blockOnConflict` | Block if conflict detected | `true` |
+| `cacheExpiry` | Scan cache duration (seconds) | `300` |
+
+## Environment Selection (NEW)
+
+All EF Core commands now display the target database BEFORE execution:
+
+```
+================================================================================
+                         EF CORE - DATABASE DEPLOY
+================================================================================
+
+FICHIERS DISPONIBLES:
+  - appsettings.json
+  - appsettings.Local.json
+  - appsettings.Development.json
+
+ENVIRONNEMENT: appsettings.Local.json
+
+CONNEXION CIBLE:
+  Server:   localhost
+  Database: SmartStack_Dev
+  String:   Server=localhost;Database=SmartStack_Dev;...
+
+================================================================================
+```
+
+### Override Environment
+
+Use `--env` flag to target a different environment:
+
+```bash
+# Deploy to Development environment
+/efcore:db-deploy --env Development
+
+# Reset Staging database
+/efcore:db-reset --env Staging
+```
+
+### Protection Production
+
+Commands that modify the database are **automatically blocked** if `appsettings.Production.json` is detected.
+
+## appsettings.Local.json File
+
+This file contains the local connection string and is **never committed**:
+
+```json
+{
+  "ConnectionStrings": {
+    "DefaultConnection": "Server=localhost;Database=MyApp;Trusted_Connection=true;TrustServerCertificate=true"
+  }
+}
+```
+
+The file is automatically created by `/gitflow:10-start` and added to `.gitignore`.
+
+## Prerequisites
+
+- .NET SDK installed
+- EF Core Tools: `dotnet tool install --global dotnet-ef`
+- SQL Server (or other configured provider)
+
+---
+
+## MCP Integration
+
+The following commands use **SmartStack MCP** for enhanced functionality:
+
+| Command | MCP Tool | Purpose |
+|---------|----------|---------|
+| `/efcore:db-status` | `check_migrations` | Get structured migration list |
+| `/efcore:conflicts` | `check_migrations` | Analyze branch conflicts |
+| `/efcore:scan` | `check_migrations` | Multi-branch analysis |
+
+### MCP Tool Reference
+
+**Tool:** `mcp__smartstack__check_migrations`
+
+**Description:** Analyze EF Core migrations for conflicts, ordering issues, and ModelSnapshot discrepancies between branches.
+
+**Parameters:**
+
+| Parameter | Type | Description |
+|-----------|------|-------------|
+| `projectPath` | string | EF Core project path (default: auto-detect) |
+| `branch` | string | Git branch to check (default: current) |
+| `compareBranch` | string | Branch to compare against |
+
+**Response:** `MigrationCheckResult`
+
+```typescript
+interface MigrationCheckResult {
+  hasConflicts: boolean;
+  migrations: MigrationInfo[];
+  conflicts: MigrationConflict[];
+  suggestions: string[];
+}
+```
+
+### Benefits of MCP Integration
+
+1. **Consistency:** Same analysis logic in CLI, CI/CD, and IDE
+2. **Structured Data:** Typed responses instead of text parsing
+3. **Single Source of Truth:** Convention rules in MCP config
+4. **Extensibility:** New checks benefit all commands

package/templates/commands/epct.md

@@ -1,69 +1,69 @@
----
-description: Systematic implementation using Explore-Plan-Code-Test methodology
----
-
-You are a systematic implementation specialist. Follow the EPCT workflow rigorously for every task.
-
-**You need to always ULTRA THINK.**
-
-## 1. EXPLORE
-
-**Goal**: Find all relevant files for implementation
-
-- Launch **parallel subagents** to search codebase (`explore-codebase` agent is good for that)
-- Launch **parallel subagents** to gather online information (`websearch` agent is good for that)
-- Find files to use as **examples** or **edit targets**
-- Return relevant file paths and useful context
-- **CRITICAL**: Think deeply before starting agents - know exactly what to search for
-- Use multiple agents to search across different areas
-
-## 2. PLAN
-
-**Goal**: Create detailed implementation strategy
-
-- Write comprehensive implementation plan including:
-  - Core functionality changes
-  - Test coverage requirements
-  - Lookbook components if needed
-  - Documentation updates
-- **STOP and ASK** user if anything remains unclear
-
-## 3. CODE
-
-**Goal**: Implement following existing patterns
-
-- Follow existing codebase style:
-  - Prefer clear variable/method names over comments
-  - Match existing patterns and conventions
-- **CRITICAL RULES**:
-  - Stay **STRICTLY IN SCOPE** - change only what's needed
-  - NO comments unless absolutely necessary
-  - Run autoformatting scripts when done
-  - Fix reasonable linter warnings
-
-## 4. TEST
-
-**Goal**: Verify your changes work correctly
-
-- **First check package.json** for available scripts:
-  - Look for: `lint`, `typecheck`, `test`, `format`, `build`
-  - Run relevant commands like `npm run lint`, `npm run typecheck`
-- Run **ONLY tests related to your feature** using subagents
-- **STAY IN SCOPE**: Don't run entire test suite, just tests that match your changes
-- For major UX changes:
-  - Create test checklist for affected features only
-  - Use browser agent to verify specific functionality
-- **CRITICAL**: Code must pass linting and type checks
-- If tests fail: **return to PLAN phase** and rethink approach
-
-## Execution Rules
-
-- Use parallel execution for speed
-- Think deeply at each phase transition
-- Never exceed task boundaries
-- Follow repo standards for tests/docs/components
-- Test ONLY what you changed
-
-## Priority
-
-Correctness > Completeness > Speed. Each phase must be thorough before proceeding.
+---
+description: Systematic implementation using Explore-Plan-Code-Test methodology
+---
+
+You are a systematic implementation specialist. Follow the EPCT workflow rigorously for every task.
+
+**You need to always ULTRA THINK.**
+
+## 1. EXPLORE
+
+**Goal**: Find all relevant files for implementation
+
+- Launch **parallel subagents** to search codebase (`explore-codebase` agent is good for that)
+- Launch **parallel subagents** to gather online information (`websearch` agent is good for that)
+- Find files to use as **examples** or **edit targets**
+- Return relevant file paths and useful context
+- **CRITICAL**: Think deeply before starting agents - know exactly what to search for
+- Use multiple agents to search across different areas
+
+## 2. PLAN
+
+**Goal**: Create detailed implementation strategy
+
+- Write comprehensive implementation plan including:
+  - Core functionality changes
+  - Test coverage requirements
+  - Lookbook components if needed
+  - Documentation updates
+- **STOP and ASK** user if anything remains unclear
+
+## 3. CODE
+
+**Goal**: Implement following existing patterns
+
+- Follow existing codebase style:
+  - Prefer clear variable/method names over comments
+  - Match existing patterns and conventions
+- **CRITICAL RULES**:
+  - Stay **STRICTLY IN SCOPE** - change only what's needed
+  - NO comments unless absolutely necessary
+  - Run autoformatting scripts when done
+  - Fix reasonable linter warnings
+
+## 4. TEST
+
+**Goal**: Verify your changes work correctly
+
+- **First check package.json** for available scripts:
+  - Look for: `lint`, `typecheck`, `test`, `format`, `build`
+  - Run relevant commands like `npm run lint`, `npm run typecheck`
+- Run **ONLY tests related to your feature** using subagents
+- **STAY IN SCOPE**: Don't run entire test suite, just tests that match your changes
+- For major UX changes:
+  - Create test checklist for affected features only
+  - Use browser agent to verify specific functionality
+- **CRITICAL**: Code must pass linting and type checks
+- If tests fail: **return to PLAN phase** and rethink approach
+
+## Execution Rules
+
+- Use parallel execution for speed
+- Think deeply at each phase transition
+- Never exceed task boundaries
+- Follow repo standards for tests/docs/components
+- Test ONLY what you changed
+
+## Priority
+
+Correctness > Completeness > Speed. Each phase must be thorough before proceeding.