@atlashub/smartstack-cli 1.10.2 → 1.12.0

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

@@ -4,177 +4,74 @@ agent: efcore-rebase-snapshot
 model: sonnet
 ---
 
-# EF Core Rebase-Snapshot - Resync with Develop
+# EF Core Rebase-Snapshot
 
-Rebases the ModelSnapshot on develop and regenerates a consolidated migration. Used when conflict is detected.
-
-**USAGE:** After `/efcore:conflicts` signals a HIGH conflict.
-
-**WARNING:** This operation modifies migration files. A backup is created automatically.
+> **Ref:** [_shared.md](_shared.md)
+> **Usage:** Après `/efcore:conflicts` HIGH
+> **WARNING:** Modifie fichiers migration. Backup automatique.
 
 ---
 
-## STEP 1: Check prerequisites
+## STEP 1: Vérifier Prérequis
 
 ```bash
 CURRENT_BRANCH=$(git branch --show-current)
-echo "Current branch: $CURRENT_BRANCH"
-
-# Check that it's a feature/release/hotfix branch
-if [[ ! $CURRENT_BRANCH =~ ^(feature|release|hotfix)/ ]]; then
-  echo "ERROR: This command can only be executed from a GitFlow branch"
-  exit 1
-fi
-
-# Check that working directory is clean
-if [ -n "$(git status --porcelain)" ]; then
-  echo "ERROR: Working directory not clean"
-  echo "Commit or stash your changes first"
-  exit 1
-fi
-
-# Find EF Core project
-CSPROJ=$(find . -name "*.csproj" -exec grep -l "Microsoft.EntityFrameworkCore" {} \; 2>/dev/null | head -1)
-if [ -z "$CSPROJ" ]; then
-  echo "ERROR: No EF Core project found"
-  exit 1
-fi
-
-PROJECT_DIR=$(dirname "$CSPROJ")
-MIGRATIONS_DIR="$PROJECT_DIR/Migrations"
-echo "Project: $PROJECT_DIR"
-echo "Migrations: $MIGRATIONS_DIR"
+[[ ! $CURRENT_BRANCH =~ ^(feature|release|hotfix)/ ]] && exit 1
+[ -n "$(git status --porcelain)" ] && { echo "Working directory non clean"; exit 1; }
+detect_efcore_project
 ```
 
 ---
 
-## STEP 2: Backup current migrations
+## STEP 2: Backup
 
 ```bash
 BACKUP_DIR=".claude/gitflow/backup/migrations/rebase_$(date +%Y%m%d_%H%M%S)"
 mkdir -p "$BACKUP_DIR"
-
-echo ""
-echo "BACKUP"
-echo "======"
-cp "$MIGRATIONS_DIR"/*.cs "$BACKUP_DIR/" 2>/dev/null
-BACKUP_COUNT=$(ls -1 "$BACKUP_DIR" | wc -l)
-echo "  $BACKUP_COUNT files backed up to $BACKUP_DIR"
+cp "$MIGRATIONS_DIR"/*.cs "$BACKUP_DIR/"
 ```
 
 ---
 
-## STEP 3: Identify this branch's migrations
+## STEP 3: Identifier Migrations de la Branche
 
 ```bash
-# Find migrations added on this branch (not on develop)
-echo ""
-echo "THIS BRANCH'S MIGRATIONS"
-echo "==========================="
-
-# Get migration list on develop
-DEVELOP_MIGRATIONS=$(git show develop:$MIGRATIONS_DIR 2>/dev/null | grep "\.cs$" | grep -v "Designer" | grep -v "Snapshot")
-
-# Local migrations
-LOCAL_MIGRATIONS=$(ls -1 "$MIGRATIONS_DIR"/*.cs 2>/dev/null | xargs -n1 basename | grep -v "Designer" | grep -v "Snapshot")
+# Migrations sur develop
+DEVELOP_MIGRATIONS=$(git show develop:$MIGRATIONS_DIR | grep "\.cs$")
 
-# New migrations (on this branch but not on develop)
-BRANCH_MIGRATIONS=""
+# Nouvelles migrations (cette branche seulement)
 for migration in $LOCAL_MIGRATIONS; do
-  if ! echo "$DEVELOP_MIGRATIONS" | grep -q "$migration"; then
-    BRANCH_MIGRATIONS="$BRANCH_MIGRATIONS $migration"
-    echo "  + $migration"
-  fi
+  echo "$DEVELOP_MIGRATIONS" | grep -q "$migration" || BRANCH_MIGRATIONS+=" $migration"
 done
-
-if [ -z "$BRANCH_MIGRATIONS" ]; then
-  echo "  No migration specific to this branch"
-  echo "  Nothing to rebase"
-  exit 0
-fi
 ```
 
 ---
 
-## STEP 4: Reset ModelSnapshot on develop
+## STEP 4: Reset ModelSnapshot sur Develop
 
 ```bash
-echo ""
-echo "RESET MODELSNAPSHOT"
-echo "==================="
-
-# Get develop's ModelSnapshot
 git fetch origin develop
-SNAPSHOT_FILE=$(find "$MIGRATIONS_DIR" -name "*ModelSnapshot.cs" | head -1)
-SNAPSHOT_NAME=$(basename "$SNAPSHOT_FILE")
-
-git checkout origin/develop -- "$MIGRATIONS_DIR/$SNAPSHOT_NAME"
-echo "  ModelSnapshot reset on develop"
+git checkout origin/develop -- "$MIGRATIONS_DIR/*ModelSnapshot.cs"
 ```
 
 ---
 
-## STEP 5: Delete this branch's migrations
+## STEP 5: Supprimer Migrations de la Branche
 
 ```bash
-echo ""
-echo "DELETE BRANCH MIGRATIONS"
-echo "=============================="
-
 for migration in $BRANCH_MIGRATIONS; do
-  BASE_NAME="${migration%.cs}"
-  rm -f "$MIGRATIONS_DIR/$BASE_NAME.cs"
-  rm -f "$MIGRATIONS_DIR/$BASE_NAME.Designer.cs"
-  echo "  - $BASE_NAME"
+  rm -f "$MIGRATIONS_DIR/${migration%.cs}.cs"
+  rm -f "$MIGRATIONS_DIR/${migration%.cs}.Designer.cs"
 done
 ```
 
 ---
 
-## STEP 6: Regenerate consolidated migration
+## STEP 6: Régénérer Migration Consolidée
 
 ```bash
-echo ""
-echo "REGENERATE MIGRATION"
-echo "======================"
-
-# Extract branch info for name
-BRANCH_TYPE=$(echo "$CURRENT_BRANCH" | cut -d'/' -f1)
-BRANCH_NAME=$(echo "$CURRENT_BRANCH" | cut -d'/' -f2 | sed 's/-/_/g' | sed 's/.*/\u&/')
-
-# Version
-VERSION=$(grep -oP '(?<=<Version>).*(?=</Version>)' "$CSPROJ" 2>/dev/null | head -1 || echo "1.0.0")
-VERSION_CLEAN=$(echo "$VERSION" | sed 's/\./_/g')
-
-# Migration name
-case $BRANCH_TYPE in
-  "feature")
-    MIGRATION_NAME="Feature_${VERSION_CLEAN}_${BRANCH_NAME}_Consolidated"
-    ;;
-  "hotfix")
-    MIGRATION_NAME="Hotfix_${VERSION_CLEAN}_${BRANCH_NAME}_Fix"
-    ;;
-  "release")
-    MIGRATION_NAME="Release_${VERSION_CLEAN}_Consolidated"
-    ;;
-  *)
-    MIGRATION_NAME="Branch_${VERSION_CLEAN}_${BRANCH_NAME}"
-    ;;
-esac
-
-echo "Name: $MIGRATION_NAME"
-
-cd "$PROJECT_DIR"
+MIGRATION_NAME="${BRANCH_TYPE}_${VERSION}_${BRANCH_NAME}_Consolidated"
 dotnet ef migrations add "$MIGRATION_NAME" --verbose
-
-if [ $? -eq 0 ]; then
-  echo "  Migration created successfully"
-else
-  echo "  ERROR: Failed to create migration"
-  echo "  Restoring backup..."
-  cp "$BACKUP_DIR"/*.cs "$MIGRATIONS_DIR/"
-  exit 1
-fi
 ```
 
 ---
@@ -182,123 +79,24 @@ fi
 ## STEP 7: Validation
 
 ```bash
-echo ""
-echo "VALIDATION"
-echo "=========="
-
-# Build
 dotnet build --no-restore
-if [ $? -ne 0 ]; then
-  echo "  ERROR: Build failed"
-  echo "  Restoring backup..."
-  cp "$BACKUP_DIR"/*.cs "$MIGRATIONS_DIR/"
-  exit 1
-fi
-echo "  Build: OK"
-
-# Check that migration can generate script
-dotnet ef migrations script --no-build > /dev/null 2>&1
-if [ $? -ne 0 ]; then
-  echo "  ERROR: Script generation failed"
-  exit 1
-fi
-echo "  Script: OK"
+dotnet ef migrations script --no-build > /dev/null
 ```
 
 ---
 
-## STEP 8: Resume
-
-**Afficher un resume apres le rebase:**
+## Résumé
 
 ```
-===============================================================================
-                         REBASE-SNAPSHOT TERMINÉ
-===============================================================================
-
-DÉTAILS
--------------------------------------------------------------------------------
-  • Branche:      {current_branch}
-  • Backup:       {backup_dir}
-
-AVANT LE REBASE
--------------------------------------------------------------------------------
-  • Migrations:   {old_migrations}
-  • Snapshot:     {old_hash}
-
-APRÈS LE REBASE
--------------------------------------------------------------------------------
-  • Migration:    {new_migration_name}
-  • Snapshot:     {new_hash} (= develop)
-
-VALIDATIONS
--------------------------------------------------------------------------------
-  ✓ ModelSnapshot synchronisé avec develop
-  ✓ Migration consolidée créée
-  ✓ Build vérifié
-  ✓ Script de migration valide
-
-===============================================================================
-                         PROCHAINES ÉTAPES
-===============================================================================
-
-1. Vérifier le contenu de la migration:
-   Ouvrir Migrations/{new_migration_name}.cs
-
-2. Tester sur la base locale:
-   /efcore:db-reset
-   /efcore:db-deploy
-
-3. Committer les changements:
-   /gitflow:3-commit
-
-===============================================================================
-                         RESTAURATION (si nécessaire)
-===============================================================================
-
-Si le rebase a causé des problèmes, restaurez le backup:
-
-   cp {backup_dir}/*.cs {migrations_dir}/
-
-===============================================================================
-```
-
-**Si le rebase échoue:**
-
+REBASE-SNAPSHOT - {branch}
+├── Backup: {backup_dir}
+├── Avant: {old_migrations}
+├── Après: {new_migration_name} (Snapshot = develop)
+├── Validations: ✓ Build, ✓ Script
+└── Prochains: /efcore:db-reset, /efcore:db-deploy, /gitflow:3-commit
 ```
-===============================================================================
-                    ÉCHEC DU REBASE-SNAPSHOT
-===============================================================================
 
-ERREUR
--------------------------------------------------------------------------------
-  ✗ {error_message}
-
-DÉTAILS
--------------------------------------------------------------------------------
-  • Branche:      {current_branch}
-  • Backup:       {backup_dir}
-
-RESTAURATION AUTOMATIQUE
--------------------------------------------------------------------------------
-  ✓ Backup restauré automatiquement
-  ✓ Fichiers originaux récupérés
-
-===============================================================================
-                         ACTIONS SUGGÉRÉES
-===============================================================================
-
-1. Vérifier les erreurs de build:
-   dotnet build
-
-2. Vérifier les conflits de modèle:
-   /efcore:conflicts
-
-3. Si problème persistant, contacter le support:
-   support@atlshub.ch
-
-===============================================================================
-```
+**Si échec:** Backup restauré automatiquement.
 
 ---
 
@@ -306,17 +104,16 @@ RESTAURATION AUTOMATIQUE
 
 | Option | Description |
 |--------|-------------|
-| `--no-backup` | Don't create backup (dangerous) |
-| `--name <name>` | Force a specific migration name |
-| `--dry-run` | Show what would be done without executing |
+| `--no-backup` | Sans backup (dangereux) |
+| `--name <name>` | Forcer nom migration |
+| `--dry-run` | Afficher sans exécuter |
 
 ---
 
-## When to use
+## Quand utiliser
 
 | Situation | Action |
 |-----------|--------|
-| `/efcore:conflicts` returns HIGH | Use rebase-snapshot |
-| Merge conflict on ModelSnapshot | Use rebase-snapshot |
-| Multiple migrations to consolidate | Use rebase-snapshot |
-| Broken migration | Use rebase-snapshot |
+| `/efcore:conflicts` HIGH | Utiliser rebase-snapshot |
+| Conflit merge sur ModelSnapshot | Utiliser rebase-snapshot |
+| Plusieurs migrations à consolider | Utiliser rebase-snapshot |

package/templates/commands/efcore/scan.md

@@ -4,49 +4,23 @@ agent: efcore-scan
 model: sonnet
 ---
 
-# EF Core Scan - Cross-Branch Migration Scanner
+# EF Core Scan
 
-Scans all active branches to detect migrations and analyze conflict risks using **SmartStack MCP**.
-
-**USAGE:** Before creating a migration or before a merge to check the status of other branches.
-
-**SECURITY:** Read-only - no modifications.
-
-**INTEGRATION:** Uses `mcp__smartstack__check_migrations` for each branch comparison.
+> **Ref:** [_shared.md](_shared.md)
+> **MCP:** `mcp__smartstack__check_migrations` pour chaque branche
+> **Type:** Read-only, aucune modification
 
 ---
 
-## STEP 1: Detect Active Worktrees
+## STEP 1: Détecter Worktrees Actifs
 
 ```bash
-# List all git worktrees
 WORKTREES=$(git worktree list --porcelain | grep "^worktree" | cut -d' ' -f2)
-
-echo "DETECTED WORKTREES"
-echo "=================="
-git worktree list
-echo ""
 ```
 
 ---
 
-## STEP 2: Invoke MCP for Each Branch
-
-> **MCP INTEGRATION:** For each active branch, call the MCP to get structured analysis.
-
-For each worktree/branch, call:
-
-```json
-{
-  "tool": "mcp__smartstack__check_migrations",
-  "parameters": {
-    "branch": "<branch_name>",
-    "compareBranch": "develop"
-  }
-}
-```
-
-**Claude instruction:** Loop through detected branches and invoke MCP:
+## STEP 2: Invoquer MCP pour Chaque Branche
 
 ```
 FOR each branch in [feature/*, hotfix/*, release/*]:
@@ -58,154 +32,42 @@ FOR each branch in [feature/*, hotfix/*, release/*]:
 
 ---
 
-## STEP 3: Aggregate Results
-
-Parse MCP responses to build summary:
-
-```typescript
-interface ScanSummary {
-  branches: BranchScan[];
-  totalMigrations: number;
-  conflictCount: number;
-  recommendedMergeOrder: string[];
-}
-
-interface BranchScan {
-  name: string;
-  migrationCount: number;
-  riskLevel: 'NONE' | 'LOW' | 'MEDIUM' | 'HIGH';
-  conflicts: MigrationConflict[];
-}
-```
-
-**Risk Level Calculation:**
+## STEP 3: Calculer Niveau Risque
 
-| Condition | Risk Level |
-|-----------|------------|
-| Snapshot identical to develop | NONE |
-| Different tables modified | LOW |
-| FK to same tables | MEDIUM |
-| Same tables/columns modified | HIGH |
+| Condition | Risque |
+|-----------|--------|
+| Snapshot = develop | NONE |
+| Tables différentes | LOW |
+| FK vers même table | MEDIUM |
+| Même tables/colonnes | HIGH |
 
 ---
 
-## STEP 4: Calculate Merge Order
-
-Based on conflict analysis, recommend merge order:
+## STEP 4: Recommander Ordre Merge
 
 ```
-1. Branches with RISK=NONE (can merge immediately)
-2. Branches with RISK=LOW (minor modifications, safe to merge)
-3. Branches with RISK=MEDIUM (order matters, merge carefully)
-4. Branches with RISK=HIGH (rebase required before merge)
+1. Branches RISK=NONE (merge immédiat)
+2. Branches RISK=LOW (modifications mineures)
+3. Branches RISK=MEDIUM (ordre important)
+4. Branches RISK=HIGH (rebase requis)
 ```
 
 ---
 
-## STEP 5: Resume
-
-**Afficher le rapport de scan:**
+## Résumé
 
 ```
-===============================================================================
-                         SCAN CROSS-BRANCH EF CORE
-===============================================================================
-
-WORKTREES DÉTECTÉS ({count})
--------------------------------------------------------------------------------
-  main/                    [main]
-  develop/                 [develop]         ← RÉFÉRENCE
-  features/user-auth/      [feature/user-auth]
-  features/add-products/   [feature/add-products]
-  hotfixes/login-fix/      [hotfix/login-fix]
-
-MIGRATIONS PAR BRANCHE
--------------------------------------------------------------------------------
-  Branche                 | Migrations | Snapshot   | vs Develop
--------------------------------------------------------------------------------
-  develop                 | 12         | a1b2c3d4   | RÉFÉRENCE
-  feature/user-auth       | 13         | e5f6g7h8   | +1 migration
-  feature/add-products    | 13         | i9j0k1l2   | +1 migration
-  hotfix/login-fix        | 12         | a1b2c3d4   | identique
--------------------------------------------------------------------------------
-
-ANALYSE DES RISQUES
--------------------------------------------------------------------------------
-  Branche                 | Risque   | Raison
--------------------------------------------------------------------------------
-  hotfix/login-fix        | AUCUN    | Snapshot = develop
-  feature/user-auth       | FAIBLE   | Tables différentes
-  feature/add-products    | MOYEN    | FK vers même table
--------------------------------------------------------------------------------
-
-===============================================================================
-                         ORDRE DE MERGE RECOMMANDÉ
-===============================================================================
-
-  #  | Branche               | Risque  | Action
--------------------------------------------------------------------------------
-  1. | hotfix/login-fix      | AUCUN   | ✓ Merge direct OK
-  2. | feature/user-auth     | FAIBLE  | ✓ Merge OK
-  3. | feature/add-products  | MOYEN   | ⚠ Après user-auth, puis rebase
--------------------------------------------------------------------------------
-
-===============================================================================
-                         PROCHAINES ÉTAPES
-===============================================================================
-
-1. Pour merger une branche sans risque:
-   /gitflow:9-merge {branch_name}
-
-2. Pour rebaser avant un merge à risque:
-   /efcore:rebase-snapshot
-
-3. Pour analyser une branche spécifique:
-   /efcore:conflicts --branch {branch_name}
-
-===============================================================================
-```
-
-**Si des conflits critiques sont détectés:**
-
-```
-===============================================================================
-                    SCAN CROSS-BRANCH - CONFLITS DÉTECTÉS
-===============================================================================
-
-WORKTREES DÉTECTÉS ({count})
--------------------------------------------------------------------------------
-  {liste des worktrees}
-
-CONFLITS CRITIQUES
--------------------------------------------------------------------------------
-  ⛔ {count} branche(s) avec des conflits HIGH ou CRITICAL
-
-DÉTAILS
--------------------------------------------------------------------------------
-{for each branch with HIGH risk}
-  [{branch_name}]
-    Risque: ÉLEVÉ
-    Raison: {conflict_reason}
-    Action: Rebase OBLIGATOIRE avant merge
-{end for}
-
-===============================================================================
-                         ACTIONS REQUISES
-===============================================================================
-
-  ⛔ Des conflits critiques empêchent le merge de certaines branches.
-
-1. Pour chaque branche à risque ÉLEVÉ:
-   git checkout {branch}
-   /efcore:rebase-snapshot
-
-2. Recréer les migrations après rebase:
-   /efcore:migration
-
-3. Re-scanner pour vérifier:
-   /efcore:scan
-
-===============================================================================
+SCAN CROSS-BRANCH
+├── Worktrees: {count}
+├── Branches avec migrations: {N}
+├── Conflits: {none/low/medium/high}
+│
+├── ORDRE MERGE RECOMMANDÉ
+│   1. {branch} - AUCUN risque - ✓ Merge OK
+│   2. {branch} - FAIBLE risque - ✓ Merge OK
+│   3. {branch} - MOYEN risque - ⚠ Après #{2}, puis rebase
+│
+└── Prochains: /gitflow:9-merge, /efcore:rebase-snapshot, /efcore:conflicts
 ```
 
 ---
@@ -214,50 +76,19 @@ DÉTAILS
 
 | Option | Description |
 |--------|-------------|
-| `--json` | Output raw JSON for CI/CD |
-| `--branch <name>` | Scan specific branch only |
-| `--verbose` | Show detailed MCP responses |
-| `--no-recommend` | Skip merge order recommendations |
+| `--json` | Output JSON pour CI/CD |
+| `--branch <name>` | Scanner branche spécifique |
+| `--verbose` | Détails MCP |
+| `--no-recommend` | Sans recommandations |
 
 ---
 
 ## CI/CD Usage
 
 ```yaml
-# GitHub Actions
 - name: Scan EF Core migrations
   run: |
-    # Claude Code will use MCP internally
     OUTPUT=$(claude-code "/efcore:scan --json")
     HIGH_RISK=$(echo $OUTPUT | jq '[.branches[] | select(.riskLevel == "HIGH")] | length')
-    if [ "$HIGH_RISK" -gt 0 ]; then
-      echo "::warning::$HIGH_RISK branches have HIGH risk migration conflicts"
-    fi
+    [ "$HIGH_RISK" -gt 0 ] && echo "::warning::$HIGH_RISK branches HIGH risk"
 ```
-
----
-
-## 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` with `hasConflicts`, `migrations[]`, `conflicts[]`, `suggestions[]`
-
----
-
-## Why MCP Integration?
-
-1. **Consistency:** Identical analysis logic for single branch (`/efcore:conflicts`) and multi-branch (`/efcore:scan`)
-2. **Accuracy:** Structured parsing instead of regex on ModelSnapshot files
-3. **Extensibility:** New conflict types added in MCP benefit all commands
-4. **Caching:** MCP can cache results for faster subsequent scans