@atlashub/smartstack-cli 1.11.0 → 1.12.0

package/templates/commands/efcore.md

@@ -4,164 +4,78 @@ description: EF Core Commands - Migration and database management
 
 # EF Core Commands
 
-Set of commands to manage Entity Framework Core: migrations, database, and seeding.
+> **Ref:** Fonctions communes dans [efcore/_shared.md](efcore/_shared.md)
+> **MCP:** `mcp__smartstack__check_migrations` pour analyse conflits
 
-> **MCP INTEGRATION:** Commands use `mcp__smartstack__check_migrations` for conflict analysis and validation.
+---
 
-## Available Commands
+## Commandes Disponibles
 
 ### 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
+| Commande | Description | Risque |
+|----------|-------------|--------|
+| `/efcore:migration` | Créer/recréer migration (1 par feature) | Low |
+| `/efcore:db-status` | Afficher statut migrations | None |
+| `/efcore:db-deploy` | Appliquer migrations | Low |
+| `/efcore:db-seed` | Peupler avec données | Low |
+| `/efcore:db-reset` | Drop + Recreate DB | **HIGH** |
 
-**Never accumulate multiple migrations on a feature.** If you modify the model:
-1. Delete the existing migration
-2. Recreate it with `/efcore:migration`
+### Cross-Branch
 
-The `/efcore:migration` command handles this automatically.
+| Commande | Description | Risque |
+|----------|-------------|--------|
+| `/efcore:scan` | Scanner toutes les branches | None |
+| `/efcore:conflicts` | Analyser conflits (BLOQUANT) | None |
+| `/efcore:rebase-snapshot` | Rebaser ModelSnapshot sur develop | Medium |
+| `/efcore:squash` | Fusionner migrations | **HIGH** |
 
-## Migration Naming
+---
 
-Pattern: `{context}_v{version}_{sequence}_{Description}` (aligned with SmartStack MCP)
+## Règle d'Or: 1 Migration par Feature
 
-| 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` |
+Si modification du modèle: supprimer et recréer la migration.
 
-> **Note:** Context is `core` for SmartStack platform tables, `extensions` for client-specific extensions.
+---
 
-## Typical Workflow
+## Workflow Typique
 
 ```
-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
+1. /gitflow:10-start feature xxx    → Worktree + appsettings.Local.json
+2. /efcore:db-deploy                → Appliquer migrations existantes
+3. ... modifications modèle ...
+4. /efcore:migration                → Créer LA migration
+5. /efcore:db-deploy                → Appliquer localement
 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:
+## Workflow Cross-Branch
 
 ```
-================================================================================
-                         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;...
-
-================================================================================
+1. /efcore:scan                → Scanner branches actives
+2. /efcore:conflicts           → Vérifier conflits (BLOQUANT)
+3. /efcore:rebase-snapshot     → Si conflit, rebaser sur develop
+4. /efcore:migration           → Créer/recréer migration
 ```
 
-### Override Environment
+---
 
-Use `--env` flag to target a different environment:
+## Sélection Environnement
 
-```bash
-# Deploy to Development environment
-/efcore:db-deploy --env Development
+Toutes les commandes affichent la base cible AVANT exécution.
 
-# Reset Staging database
-/efcore:db-reset --env Staging
-```
+| Priorité | Fichier |
+|----------|---------|
+| 1 | `--env {Environment}` flag |
+| 2 | `appsettings.Local.json` (défaut) |
 
-### Protection Production
+**Protection:** Commandes destructives bloquées si Production détecté.
 
-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**:
+## appsettings.Local.json
 
 ```json
 {
@@ -171,54 +85,12 @@ This file contains the local connection string and is **never committed**:
 }
 ```
 
-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)
+Créé automatiquement par `/gitflow:10-start`, ajouté à `.gitignore`.
 
 ---
 
-## MCP Integration
-
-The following commands use **SmartStack MCP** for enhanced functionality:
+## Prérequis
 
-| 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
+- .NET SDK installé
+- EF Core Tools: `dotnet tool install --global dotnet-ef`
+- SQL Server (ou provider configuré)