@atlashub/smartstack-cli 1.5.1 → 1.5.2

package/templates/commands/efcore/_env-check.md

@@ -1,153 +1,153 @@
-# EF Core Environment Check (Shared Step)
-
-> **Usage:** Include ce step dans toutes les commandes EF Core qui interagissent avec la base de donnees.
-
----
-
-## STEP 0: Verification environnement et connexion
-
-### 0.1 Detecter les fichiers appsettings disponibles
-
-```bash
-# Scanner les fichiers appsettings dans le projet API
-API_DIR=$(find . -type d -name "*.Api" -o -name "*Web" | head -1)
-if [ -z "$API_DIR" ]; then
-  API_DIR="."
-fi
-
-# Lister tous les appsettings
-APPSETTINGS_FILES=$(find "$API_DIR" -maxdepth 1 -name "appsettings*.json" 2>/dev/null | sort)
-```
-
-### 0.2 Determiner l'environnement a utiliser
-
-**Priorite:**
-1. Flag `--env {Environment}` si fourni
-2. `appsettings.Local.json` (defaut recommande)
-3. Erreur si aucun fichier trouve
-
-```bash
-# Logique de selection
-ENV_FLAG="$1"  # --env Development par exemple
-
-if [ -n "$ENV_FLAG" ]; then
-  SELECTED_ENV="appsettings.${ENV_FLAG}.json"
-elif [ -f "$API_DIR/appsettings.Local.json" ]; then
-  SELECTED_ENV="appsettings.Local.json"
-else
-  echo "ERROR: Aucun fichier appsettings trouve"
-  echo "  Creez appsettings.Local.json ou utilisez --env {Environment}"
-  exit 1
-fi
-
-# Verifier que le fichier existe
-if [ ! -f "$API_DIR/$SELECTED_ENV" ]; then
-  echo "ERROR: $SELECTED_ENV non trouve dans $API_DIR"
-  exit 1
-fi
-```
-
-### 0.3 Extraire et afficher la connection string
-
-```bash
-# Extraire la connection string (PowerShell pour parsing JSON fiable)
-CONNECTION_STRING=$(powershell -Command "
-  \$json = Get-Content '$API_DIR/$SELECTED_ENV' | ConvertFrom-Json
-  \$json.ConnectionStrings.DefaultConnection
-")
-
-# Extraire le nom de la base de donnees
-DATABASE_NAME=$(echo "$CONNECTION_STRING" | grep -oP 'Database=\K[^;]+' || echo "Unknown")
-SERVER_NAME=$(echo "$CONNECTION_STRING" | grep -oP 'Server=\K[^;]+' || echo "Unknown")
-
-# Masquer le mot de passe si present
-CONNECTION_MASKED=$(echo "$CONNECTION_STRING" | sed 's/Password=[^;]*/Password=****/g')
-```
-
-### 0.4 Afficher le resume
-
-```
-================================================================================
-                         EF CORE - ENVIRONNEMENT
-================================================================================
-
-FICHIERS DISPONIBLES:
-{liste des appsettings detectes}
-
-SELECTION: {SELECTED_ENV} {(defaut) si Local}
-
-CONNEXION:
-  Server:   {SERVER_NAME}
-  Database: {DATABASE_NAME}
-  String:   {CONNECTION_MASKED}
-
-================================================================================
-```
-
-### 0.5 Protection Production
-
-```bash
-# Bloquer si Production detecte (sauf pour db-status qui est read-only)
-if [[ "$SELECTED_ENV" == *"Production"* ]]; then
-  echo "================================================================================
-                         BLOQUE - ENVIRONNEMENT PRODUCTION
-================================================================================
-
-Cette commande est bloquee pour proteger les donnees de production.
-
-OPTIONS:
-1. Utilisez un environnement non-production
-2. Contactez support@atlshub.ch pour assistance
-
-================================================================================
-"
-  exit 1
-fi
-```
-
-### 0.6 Confirmation (pour commandes destructives)
-
-> **Note:** Utiliser uniquement pour db-reset, db-seed, et autres commandes destructives.
-
-```javascript
-AskUserQuestion({
-  questions: [{
-    question: "Confirmer l'execution sur cette base de donnees?",
-    header: "Confirm",
-    options: [
-      { label: "Oui, continuer", description: "Executer sur " + DATABASE_NAME },
-      { label: "Non, annuler", description: "Arreter l'execution" }
-    ],
-    multiSelect: false
-  }]
-})
-```
-
----
-
-## Variables exportees
-
-Apres ce step, les variables suivantes sont disponibles:
-
-| Variable | Description |
-|----------|-------------|
-| `SELECTED_ENV` | Fichier appsettings utilise |
-| `CONNECTION_STRING` | Connection string complete |
-| `CONNECTION_MASKED` | Connection string masquee |
-| `DATABASE_NAME` | Nom de la base de donnees |
-| `SERVER_NAME` | Nom du serveur |
-| `API_DIR` | Repertoire du projet API |
-
----
-
-## Utilisation dans les commandes
-
-```markdown
-## STEP 0: Verification environnement
-
-> **Include:** `_env-check.md`
-
-{Executer les etapes 0.1 a 0.4}
-{Executer 0.5 si commande modifie la base}
-{Executer 0.6 si commande est destructive}
-```
+# EF Core Environment Check (Shared Step)
+
+> **Usage:** Include ce step dans toutes les commandes EF Core qui interagissent avec la base de donnees.
+
+---
+
+## STEP 0: Verification environnement et connexion
+
+### 0.1 Detecter les fichiers appsettings disponibles
+
+```bash
+# Scanner les fichiers appsettings dans le projet API
+API_DIR=$(find . -type d -name "*.Api" -o -name "*Web" | head -1)
+if [ -z "$API_DIR" ]; then
+  API_DIR="."
+fi
+
+# Lister tous les appsettings
+APPSETTINGS_FILES=$(find "$API_DIR" -maxdepth 1 -name "appsettings*.json" 2>/dev/null | sort)
+```
+
+### 0.2 Determiner l'environnement a utiliser
+
+**Priorite:**
+1. Flag `--env {Environment}` si fourni
+2. `appsettings.Local.json` (defaut recommande)
+3. Erreur si aucun fichier trouve
+
+```bash
+# Logique de selection
+ENV_FLAG="$1"  # --env Development par exemple
+
+if [ -n "$ENV_FLAG" ]; then
+  SELECTED_ENV="appsettings.${ENV_FLAG}.json"
+elif [ -f "$API_DIR/appsettings.Local.json" ]; then
+  SELECTED_ENV="appsettings.Local.json"
+else
+  echo "ERROR: Aucun fichier appsettings trouve"
+  echo "  Creez appsettings.Local.json ou utilisez --env {Environment}"
+  exit 1
+fi
+
+# Verifier que le fichier existe
+if [ ! -f "$API_DIR/$SELECTED_ENV" ]; then
+  echo "ERROR: $SELECTED_ENV non trouve dans $API_DIR"
+  exit 1
+fi
+```
+
+### 0.3 Extraire et afficher la connection string
+
+```bash
+# Extraire la connection string (PowerShell pour parsing JSON fiable)
+CONNECTION_STRING=$(powershell -Command "
+  \$json = Get-Content '$API_DIR/$SELECTED_ENV' | ConvertFrom-Json
+  \$json.ConnectionStrings.DefaultConnection
+")
+
+# Extraire le nom de la base de donnees
+DATABASE_NAME=$(echo "$CONNECTION_STRING" | grep -oP 'Database=\K[^;]+' || echo "Unknown")
+SERVER_NAME=$(echo "$CONNECTION_STRING" | grep -oP 'Server=\K[^;]+' || echo "Unknown")
+
+# Masquer le mot de passe si present
+CONNECTION_MASKED=$(echo "$CONNECTION_STRING" | sed 's/Password=[^;]*/Password=****/g')
+```
+
+### 0.4 Afficher le resume
+
+```
+================================================================================
+                         EF CORE - ENVIRONNEMENT
+================================================================================
+
+FICHIERS DISPONIBLES:
+{liste des appsettings detectes}
+
+SELECTION: {SELECTED_ENV} {(defaut) si Local}
+
+CONNEXION:
+  Server:   {SERVER_NAME}
+  Database: {DATABASE_NAME}
+  String:   {CONNECTION_MASKED}
+
+================================================================================
+```
+
+### 0.5 Protection Production
+
+```bash
+# Bloquer si Production detecte (sauf pour db-status qui est read-only)
+if [[ "$SELECTED_ENV" == *"Production"* ]]; then
+  echo "================================================================================
+                         BLOQUE - ENVIRONNEMENT PRODUCTION
+================================================================================
+
+Cette commande est bloquee pour proteger les donnees de production.
+
+OPTIONS:
+1. Utilisez un environnement non-production
+2. Contactez support@atlshub.ch pour assistance
+
+================================================================================
+"
+  exit 1
+fi
+```
+
+### 0.6 Confirmation (pour commandes destructives)
+
+> **Note:** Utiliser uniquement pour db-reset, db-seed, et autres commandes destructives.
+
+```javascript
+AskUserQuestion({
+  questions: [{
+    question: "Confirmer l'execution sur cette base de donnees?",
+    header: "Confirm",
+    options: [
+      { label: "Oui, continuer", description: "Executer sur " + DATABASE_NAME },
+      { label: "Non, annuler", description: "Arreter l'execution" }
+    ],
+    multiSelect: false
+  }]
+})
+```
+
+---
+
+## Variables exportees
+
+Apres ce step, les variables suivantes sont disponibles:
+
+| Variable | Description |
+|----------|-------------|
+| `SELECTED_ENV` | Fichier appsettings utilise |
+| `CONNECTION_STRING` | Connection string complete |
+| `CONNECTION_MASKED` | Connection string masquee |
+| `DATABASE_NAME` | Nom de la base de donnees |
+| `SERVER_NAME` | Nom du serveur |
+| `API_DIR` | Repertoire du projet API |
+
+---
+
+## Utilisation dans les commandes
+
+```markdown
+## STEP 0: Verification environnement
+
+> **Include:** `_env-check.md`
+
+{Executer les etapes 0.1 a 0.4}
+{Executer 0.5 si commande modifie la base}
+{Executer 0.6 si commande est destructive}
+```

package/templates/commands/efcore/conflicts.md

@@ -1,186 +1,186 @@
----
-description: Analyze conflicts before merge (BLOCKING if conflict detected)
-agent: efcore-conflicts
-model: sonnet
----
-
-# EF Core Conflicts - Cross-Branch Conflict Analysis
-
-Analyzes potential conflicts between current branch and target branch using **SmartStack MCP**.
-
-**USAGE:** Before a merge or commit to ensure there are no migration conflicts.
-
-**BEHAVIOR:** Returns exit code 1 if conflict detected (blocks merge/commit).
-
-**INTEGRATION:** Uses `mcp__smartstack__check_migrations` for structured analysis.
-
----
-
-## STEP 1: Invoke MCP check_migrations
-
-> **MCP INTEGRATION:** This command delegates conflict analysis to the SmartStack MCP server
-> which provides structured, consistent analysis across all SmartStack projects.
-
-```
-CALL mcp__smartstack__check_migrations WITH:
-  - branch: {current branch}
-  - compareBranch: "develop" (or specified target)
-```
-
-**Claude instruction:** Use the MCP tool `mcp__smartstack__check_migrations` with parameters:
-
-```json
-{
-  "branch": "<current_branch>",
-  "compareBranch": "develop"
-}
-```
-
----
-
-## STEP 2: Parse MCP Response
-
-The MCP returns a structured `MigrationCheckResult`:
-
-```typescript
-interface MigrationCheckResult {
-  hasConflicts: boolean;
-  migrations: MigrationInfo[];
-  conflicts: MigrationConflict[];
-  suggestions: string[];
-}
-
-interface MigrationConflict {
-  type: 'order' | 'snapshot' | 'dependency' | 'naming';
-  description: string;
-  files: string[];
-  resolution: string;
-}
-```
-
----
-
-## STEP 3: Evaluate Conflict Level
-
-Based on MCP response:
-
-| Conflict Type | Level | Action |
-|---------------|-------|--------|
-| `naming` | LOW | Warning only |
-| `order` | MEDIUM | Warning, suggest reorder |
-| `dependency` | HIGH | Block merge |
-| `snapshot` | CRITICAL | Block merge, require rebase |
-
----
-
-## STEP 4: Display Results
-
-**If `hasConflicts: false`:**
-
-```
-================================================================================
-                    EF CORE CONFLICT ANALYSIS (via MCP)
-================================================================================
-
-BRANCH: {current_branch}
-TARGET: develop
-
-STATUS: OK - No conflicts detected
-
-Migrations: {count}
-ModelSnapshot: Synchronized
-
-================================================================================
-```
-
-**If `hasConflicts: true`:**
-
-```
-================================================================================
-                    EF CORE CONFLICT ANALYSIS (via MCP)
-================================================================================
-
-BRANCH: {current_branch}
-TARGET: develop
-
-STATUS: CONFLICT DETECTED
-
-CONFLICTS FOUND:
-{for each conflict in conflicts}
-  [{conflict.type}] {conflict.description}
-    Files: {conflict.files.join(', ')}
-    Resolution: {conflict.resolution}
-{end for}
-
-SUGGESTIONS:
-{for each suggestion in suggestions}
-  - {suggestion}
-{end for}
-
-================================================================================
-BLOCKING: Merge not allowed until conflicts are resolved.
-================================================================================
-
-RESOLUTION OPTIONS:
-  /efcore:rebase-snapshot    Rebase ModelSnapshot on develop (recommended)
-  /efcore:conflicts --force  Ignore and proceed (not recommended)
-
-================================================================================
-```
-
----
-
-## STEP 5: Exit Code
-
-```bash
-if [ "$HAS_CONFLICTS" = "true" ]; then
-  exit 1  # BLOCKING
-else
-  exit 0  # OK
-fi
-```
-
----
-
-## Options
-
-| Option | Description |
-|--------|-------------|
-| `--force` | Ignore conflict (not recommended) |
-| `--target <branch>` | Compare with branch other than develop |
-| `--json` | Output raw MCP JSON response |
-
----
-
-## Exit Codes
-
-| Code | Meaning |
-|------|---------|
-| 0 | No conflict or minor conflict |
-| 1 | Conflict detected - merge blocked |
-| 2 | MCP connection error |
-
----
-
-## 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 |
-
----
-
-## Why MCP Integration?
-
-1. **Consistency:** Same analysis logic across CLI, CI/CD, and IDE
-2. **Maintainability:** Single source of truth in MCP server
-3. **Structured Output:** Typed responses instead of bash text parsing
-4. **Extensibility:** Easy to add new conflict types in one place
+---
+description: Analyze conflicts before merge (BLOCKING if conflict detected)
+agent: efcore-conflicts
+model: sonnet
+---
+
+# EF Core Conflicts - Cross-Branch Conflict Analysis
+
+Analyzes potential conflicts between current branch and target branch using **SmartStack MCP**.
+
+**USAGE:** Before a merge or commit to ensure there are no migration conflicts.
+
+**BEHAVIOR:** Returns exit code 1 if conflict detected (blocks merge/commit).
+
+**INTEGRATION:** Uses `mcp__smartstack__check_migrations` for structured analysis.
+
+---
+
+## STEP 1: Invoke MCP check_migrations
+
+> **MCP INTEGRATION:** This command delegates conflict analysis to the SmartStack MCP server
+> which provides structured, consistent analysis across all SmartStack projects.
+
+```
+CALL mcp__smartstack__check_migrations WITH:
+  - branch: {current branch}
+  - compareBranch: "develop" (or specified target)
+```
+
+**Claude instruction:** Use the MCP tool `mcp__smartstack__check_migrations` with parameters:
+
+```json
+{
+  "branch": "<current_branch>",
+  "compareBranch": "develop"
+}
+```
+
+---
+
+## STEP 2: Parse MCP Response
+
+The MCP returns a structured `MigrationCheckResult`:
+
+```typescript
+interface MigrationCheckResult {
+  hasConflicts: boolean;
+  migrations: MigrationInfo[];
+  conflicts: MigrationConflict[];
+  suggestions: string[];
+}
+
+interface MigrationConflict {
+  type: 'order' | 'snapshot' | 'dependency' | 'naming';
+  description: string;
+  files: string[];
+  resolution: string;
+}
+```
+
+---
+
+## STEP 3: Evaluate Conflict Level
+
+Based on MCP response:
+
+| Conflict Type | Level | Action |
+|---------------|-------|--------|
+| `naming` | LOW | Warning only |
+| `order` | MEDIUM | Warning, suggest reorder |
+| `dependency` | HIGH | Block merge |
+| `snapshot` | CRITICAL | Block merge, require rebase |
+
+---
+
+## STEP 4: Display Results
+
+**If `hasConflicts: false`:**
+
+```
+================================================================================
+                    EF CORE CONFLICT ANALYSIS (via MCP)
+================================================================================
+
+BRANCH: {current_branch}
+TARGET: develop
+
+STATUS: OK - No conflicts detected
+
+Migrations: {count}
+ModelSnapshot: Synchronized
+
+================================================================================
+```
+
+**If `hasConflicts: true`:**
+
+```
+================================================================================
+                    EF CORE CONFLICT ANALYSIS (via MCP)
+================================================================================
+
+BRANCH: {current_branch}
+TARGET: develop
+
+STATUS: CONFLICT DETECTED
+
+CONFLICTS FOUND:
+{for each conflict in conflicts}
+  [{conflict.type}] {conflict.description}
+    Files: {conflict.files.join(', ')}
+    Resolution: {conflict.resolution}
+{end for}
+
+SUGGESTIONS:
+{for each suggestion in suggestions}
+  - {suggestion}
+{end for}
+
+================================================================================
+BLOCKING: Merge not allowed until conflicts are resolved.
+================================================================================
+
+RESOLUTION OPTIONS:
+  /efcore:rebase-snapshot    Rebase ModelSnapshot on develop (recommended)
+  /efcore:conflicts --force  Ignore and proceed (not recommended)
+
+================================================================================
+```
+
+---
+
+## STEP 5: Exit Code
+
+```bash
+if [ "$HAS_CONFLICTS" = "true" ]; then
+  exit 1  # BLOCKING
+else
+  exit 0  # OK
+fi
+```
+
+---
+
+## Options
+
+| Option | Description |
+|--------|-------------|
+| `--force` | Ignore conflict (not recommended) |
+| `--target <branch>` | Compare with branch other than develop |
+| `--json` | Output raw MCP JSON response |
+
+---
+
+## Exit Codes
+
+| Code | Meaning |
+|------|---------|
+| 0 | No conflict or minor conflict |
+| 1 | Conflict detected - merge blocked |
+| 2 | MCP connection error |
+
+---
+
+## 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 |
+
+---
+
+## Why MCP Integration?
+
+1. **Consistency:** Same analysis logic across CLI, CI/CD, and IDE
+2. **Maintainability:** Single source of truth in MCP server
+3. **Structured Output:** Typed responses instead of bash text parsing
+4. **Extensibility:** Easy to add new conflict types in one place