@atlashub/smartstack-cli 3.39.0 → 3.41.0

package/templates/skills/gitflow/references/init-name-normalization.md

@@ -1,103 +1,103 @@
-# Project Name Normalization (INTELLIGENT)
-
-**ALWAYS normalize, even if user chose the detected name.**
-
-## Step 1: Parse input into words
-
-Split the raw input on any separator: spaces, hyphens, underscores, dots, camelCase boundaries.
-
-| Raw input | Parsed words |
-|-----------|-------------|
-| `mon super projet` | `["mon", "super", "projet"]` |
-| `gestion-des-stocks` | `["gestion", "des", "stocks"]` |
-| `my_awesome_app` | `["my", "awesome", "app"]` |
-| `SmartStack.App` | `["Smart", "Stack", "App"]` |
-| `userManagement` | `["user", "Management"]` |
-
-## Step 2: Language detection and spell check
-
-For EACH word, you MUST:
-1. **Detect the language** (French, English, or technical/proper noun)
-2. **Check spelling** - flag obvious typos
-3. **Suggest corrections** if misspelled
-
-| Word | Language | Spelling | Suggestion |
-|------|----------|----------|------------|
-| `gestion` | FR | OK | - |
-| `gestoin` | FR | typo | -> `gestion` |
-| `managment` | EN | typo | -> `management` |
-| `SmartStack` | Proper noun | OK | - |
-| `auth` | EN (abbreviation) | OK | - |
-
-**If typos detected**, ask the user BEFORE generating variants:
-
-```yaml
-AskUserQuestion:
-  - header: "Spelling"
-    question: "Corrections detected. Accept?"
-    options:
-      - label: "Accept corrections (Recommended)"
-        description: "'gestoin' -> 'gestion', 'managment' -> 'management'"
-      - label: "Keep original"
-        description: "Use the name as typed"
-    multiSelect: false
-```
-
-## Step 3: Generate all name variants
-
-From the cleaned words, generate ALL variants:
-
-| Variant | Format | Best for |
-|---------|--------|----------|
-| PascalCase.Dot | `Gestion.Des.Stocks` | .NET namespace, C# project, folder name |
-| PascalCase | `GestionDesStocks` | Class name, assembly name |
-| kebab-case | `gestion-des-stocks` | Git repo, npm package, URL slug |
-| snake_case | `gestion_des_stocks` | Database, Python, file system |
-
-## Step 4: Ask user to choose the PRIMARY format
-
-```yaml
-AskUserQuestion:
-  - header: "Format"
-    question: "Which format for the project name?"
-    options:
-      - label: "PascalCase.Dot (Recommended)"
-        description: "{PascalCase.Dot variant} - .NET convention"
-      - label: "PascalCase"
-        description: "{PascalCase variant} - single word"
-      - label: "kebab-case"
-        description: "{kebab-case variant} - git/npm convention"
-      - label: "snake_case"
-        description: "{snake_case variant} - database/python convention"
-    multiSelect: false
-```
-
-## Step 5: Store all derived names
-
-Regardless of the chosen primary format, ALL variants are generated and stored:
-
-```json
-{
-  "PROJECT_NAME": "{chosen format}",
-  "PROJECT_VARIANTS": {
-    "pascalCaseDot": "Gestion.Des.Stocks",
-    "pascalCase": "GestionDesStocks",
-    "kebabCase": "gestion-des-stocks",
-    "snakeCase": "gestion_des_stocks",
-    "displayName": "Gestion Des Stocks",
-    "words": ["gestion", "des", "stocks"],
-    "language": "fr"
-  }
-}
-```
-
-## Real-world examples
-
-| User types | PascalCase.Dot | kebab-case | PascalCase |
-|-----------|---------------|------------|------------|
-| `smart stack app` | `SmartStack.App` | `smart-stack-app` | `SmartStackApp` |
-| `gestion-des-stocks` | `Gestion.Des.Stocks` | `gestion-des-stocks` | `GestionDesStocks` |
-| `Mon Projet V2` | `Mon.Projet.V2` | `mon-projet-v2` | `MonProjetV2` |
-| `user auth module` | `User.Auth.Module` | `user-auth-module` | `UserAuthModule` |
-| `PROJET TEST` | `Projet.Test` | `projet-test` | `ProjetTest` |
-| `e-commerce platform` | `ECommerce.Platform` | `e-commerce-platform` | `ECommercePlatform` |
+# Project Name Normalization (INTELLIGENT)
+
+**ALWAYS normalize, even if user chose the detected name.**
+
+## Step 1: Parse input into words
+
+Split the raw input on any separator: spaces, hyphens, underscores, dots, camelCase boundaries.
+
+| Raw input | Parsed words |
+|-----------|-------------|
+| `mon super projet` | `["mon", "super", "projet"]` |
+| `gestion-des-stocks` | `["gestion", "des", "stocks"]` |
+| `my_awesome_app` | `["my", "awesome", "app"]` |
+| `SmartStack.App` | `["Smart", "Stack", "App"]` |
+| `userManagement` | `["user", "Management"]` |
+
+## Step 2: Language detection and spell check
+
+For EACH word, you MUST:
+1. **Detect the language** (French, English, or technical/proper noun)
+2. **Check spelling** - flag obvious typos
+3. **Suggest corrections** if misspelled
+
+| Word | Language | Spelling | Suggestion |
+|------|----------|----------|------------|
+| `gestion` | FR | OK | - |
+| `gestoin` | FR | typo | -> `gestion` |
+| `managment` | EN | typo | -> `management` |
+| `SmartStack` | Proper noun | OK | - |
+| `auth` | EN (abbreviation) | OK | - |
+
+**If typos detected**, ask the user BEFORE generating variants:
+
+```yaml
+AskUserQuestion:
+  - header: "Spelling"
+    question: "Corrections detected. Accept?"
+    options:
+      - label: "Accept corrections (Recommended)"
+        description: "'gestoin' -> 'gestion', 'managment' -> 'management'"
+      - label: "Keep original"
+        description: "Use the name as typed"
+    multiSelect: false
+```
+
+## Step 3: Generate all name variants
+
+From the cleaned words, generate ALL variants:
+
+| Variant | Format | Best for |
+|---------|--------|----------|
+| PascalCase.Dot | `Gestion.Des.Stocks` | .NET namespace, C# project, folder name |
+| PascalCase | `GestionDesStocks` | Class name, assembly name |
+| kebab-case | `gestion-des-stocks` | Git repo, npm package, URL slug |
+| snake_case | `gestion_des_stocks` | Database, Python, file system |
+
+## Step 4: Ask user to choose the PRIMARY format
+
+```yaml
+AskUserQuestion:
+  - header: "Format"
+    question: "Which format for the project name?"
+    options:
+      - label: "PascalCase.Dot (Recommended)"
+        description: "{PascalCase.Dot variant} - .NET convention"
+      - label: "PascalCase"
+        description: "{PascalCase variant} - single word"
+      - label: "kebab-case"
+        description: "{kebab-case variant} - git/npm convention"
+      - label: "snake_case"
+        description: "{snake_case variant} - database/python convention"
+    multiSelect: false
+```
+
+## Step 5: Store all derived names
+
+Regardless of the chosen primary format, ALL variants are generated and stored:
+
+```json
+{
+  "PROJECT_NAME": "{chosen format}",
+  "PROJECT_VARIANTS": {
+    "pascalCaseDot": "Gestion.Des.Stocks",
+    "pascalCase": "GestionDesStocks",
+    "kebabCase": "gestion-des-stocks",
+    "snakeCase": "gestion_des_stocks",
+    "displayName": "Gestion Des Stocks",
+    "words": ["gestion", "des", "stocks"],
+    "language": "fr"
+  }
+}
+```
+
+## Real-world examples
+
+| User types | PascalCase.Dot | kebab-case | PascalCase |
+|-----------|---------------|------------|------------|
+| `smart stack app` | `SmartStack.App` | `smart-stack-app` | `SmartStackApp` |
+| `gestion-des-stocks` | `Gestion.Des.Stocks` | `gestion-des-stocks` | `GestionDesStocks` |
+| `Mon Projet V2` | `Mon.Projet.V2` | `mon-projet-v2` | `MonProjetV2` |
+| `user auth module` | `User.Auth.Module` | `user-auth-module` | `UserAuthModule` |
+| `PROJET TEST` | `Projet.Test` | `projet-test` | `ProjetTest` |
+| `e-commerce platform` | `ECommerce.Platform` | `e-commerce-platform` | `ECommercePlatform` |

package/templates/skills/gitflow/references/init-questions.md

@@ -1,185 +1,185 @@
-# MANDATORY User Questions for Init
-
-All questions must be asked in order. See step-init.md for context on when each is asked.
-
-## Question 1: Repository URL
-
-**⛔ ALWAYS ask, even if URL was detected:**
-
-```yaml
-AskUserQuestion:
-  - header: "Repository"
-    question: "Repository URL? (detected: {DETECTED_URL})"
-    options:
-      - label: "Use detected URL (Recommended)"
-        description: "{DETECTED_URL}"
-      - label: "Enter GitHub URL"
-        description: "https://github.com/org/repo.git"
-      - label: "Enter Azure DevOps URL"
-        description: "https://dev.azure.com/org/project/_git/repo"
-      - label: "Local only (no remote)"
-        description: "Initialize without remote (limited features)"
-    multiSelect: false
-```
-
-**⛔ FOLLOW-UP: If user selects "Enter GitHub URL" or "Enter Azure DevOps URL":**
-
-The selected option is just a choice, NOT the actual URL. You MUST ask a follow-up question:
-
-```yaml
-AskUserQuestion:
-  - header: "URL"
-    question: "Enter the repository URL:"
-    options:
-      - label: "https://github.com/org/repo.git"
-        description: "Example GitHub format"
-      - label: "https://dev.azure.com/org/project/_git/repo"
-        description: "Example Azure DevOps format"
-    multiSelect: false
-```
-
-The user will type the actual URL via "Other". Then:
-- Validate format
-- Update `{REPO_URL}` and `{GIT_PROVIDER}`
-
-## Question 2: Root Folder
-
-**⛔ ALWAYS ask where to create THIS project's structure:**
-
-**If sibling projects exist, show where it fits:**
-
-```
-{WORKSPACE_DIR}/
-├── SmartStack.app/    ✅ (gitflow)
-├── SmartStack.mcp/    ✅ (gitflow)
-├── SmartStack.cli/    ✅ (gitflow)
-└── NewProject/        ← THIS PROJECT
-    ├── .bare/
-    ├── 01-Main/
-    ├── 02-Develop/
-    ├── features/
-    ├── releases/
-    └── hotfixes/
-```
-
-```yaml
-AskUserQuestion:
-  - header: "Location"
-    question: "Root folder for THIS project? (worktrees will be created here)"
-    options:
-      - label: "Use parent folder (Recommended)"
-        description: "{DETECTED_FOLDER}/ - consistent with {#SIBLING_PROJECTS} sibling project(s)"
-      - label: "Use current folder"
-        description: "$(pwd)/ - Will create subfolders here"
-      - label: "Custom path"
-        description: "Specify a different location"
-    multiSelect: false
-```
-
-**⛔ FOLLOW-UP: If user selects "Custom path":**
-
-You MUST ask a follow-up question to get the actual path:
-
-```yaml
-AskUserQuestion:
-  - header: "Path"
-    question: "Enter the full path for the project root folder:"
-    options:
-      - label: "{DETECTED_FOLDER}/"
-        description: "Parent of current directory"
-      - label: "{WORKSPACE_DIR}/"
-        description: "Workspace root"
-    multiSelect: false
-```
-
-The user will type the actual path via "Other". Validate the path exists or can be created.
-
-**Explain the structure that will be created for this project:**
-
-```
-{ROOT_FOLDER}/
-├── .bare/                 # Git bare repository (this repo only)
-├── 01-Main/               # Worktree: main branch
-├── 02-Develop/            # Worktree: develop branch
-├── features/              # Feature branch worktrees
-├── releases/              # Release branch worktrees
-└── hotfixes/              # Hotfix branch worktrees
-```
-
-## Question 3: Project Name
-
-**⛔ ALWAYS ask to confirm project name:**
-
-```yaml
-AskUserQuestion:
-  - header: "Project"
-    question: "Project name? (detected: {DETECTED_NAME})"
-    options:
-      - label: "Use detected name (Recommended)"
-        description: "Project: {DETECTED_NAME}"
-      - label: "Custom name"
-        description: "Specify a different project name"
-    multiSelect: false
-```
-
-**⛔ FOLLOW-UP: If user selects "Custom name":**
-
-You MUST ask a follow-up question to get the actual name:
-
-```yaml
-AskUserQuestion:
-  - header: "Name"
-    question: "Enter the project name:"
-    options:
-      - label: "{DETECTED_NAME}"
-        description: "Detected from repository"
-      - label: "{DETECTED_NAME}-v2"
-        description: "Variant of detected name"
-    multiSelect: false
-```
-
-The user will type the actual name via "Other". Use this raw input for step 6b (normalization).
-
-## Question 4: Existing Configuration
-
-**If `ALREADY_INITIALIZED` = true:**
-
-Display current configuration and ask what to do:
-
-```yaml
-AskUserQuestion:
-  - header: "Existing"
-    question: "GitFlow is already initialized. Current config will be shown. What do you want to do?"
-    options:
-      - label: "Reconfigure (Recommended)"
-        description: "Review and update all settings"
-      - label: "Repair"
-        description: "Fix missing directories only"
-      - label: "View only"
-        description: "Display current config and exit"
-      - label: "Cancel"
-        description: "Exit without changes"
-    multiSelect: false
-```
-
-**Handle choices:**
-- **Reconfigure**: Continue to step 4 (will ask all questions again)
-- **Repair**: Check directories, fix missing ones, exit
-- **View only**: Display config, exit
-- **Cancel**: Exit immediately
-
-## Question 5: Worktree Mode
-
-```yaml
-AskUserQuestion:
-  - header: "Worktrees"
-    question: "How should worktrees be organized?"
-    options:
-      - label: "Organized (Recommended)"
-        description: "01-Main, 02-Develop, features/, releases/, hotfixes/"
-      - label: "Simple"
-        description: "main/, develop/, features/, releases/, hotfixes/"
-      - label: "Disabled"
-        description: "No worktrees, use git checkout (not recommended)"
-    multiSelect: false
-```
+# MANDATORY User Questions for Init
+
+All questions must be asked in order. See step-init.md for context on when each is asked.
+
+## Question 1: Repository URL
+
+**⛔ ALWAYS ask, even if URL was detected:**
+
+```yaml
+AskUserQuestion:
+  - header: "Repository"
+    question: "Repository URL? (detected: {DETECTED_URL})"
+    options:
+      - label: "Use detected URL (Recommended)"
+        description: "{DETECTED_URL}"
+      - label: "Enter GitHub URL"
+        description: "https://github.com/org/repo.git"
+      - label: "Enter Azure DevOps URL"
+        description: "https://dev.azure.com/org/project/_git/repo"
+      - label: "Local only (no remote)"
+        description: "Initialize without remote (limited features)"
+    multiSelect: false
+```
+
+**⛔ FOLLOW-UP: If user selects "Enter GitHub URL" or "Enter Azure DevOps URL":**
+
+The selected option is just a choice, NOT the actual URL. You MUST ask a follow-up question:
+
+```yaml
+AskUserQuestion:
+  - header: "URL"
+    question: "Enter the repository URL:"
+    options:
+      - label: "https://github.com/org/repo.git"
+        description: "Example GitHub format"
+      - label: "https://dev.azure.com/org/project/_git/repo"
+        description: "Example Azure DevOps format"
+    multiSelect: false
+```
+
+The user will type the actual URL via "Other". Then:
+- Validate format
+- Update `{REPO_URL}` and `{GIT_PROVIDER}`
+
+## Question 2: Root Folder
+
+**⛔ ALWAYS ask where to create THIS project's structure:**
+
+**If sibling projects exist, show where it fits:**
+
+```
+{WORKSPACE_DIR}/
+├── SmartStack.app/    ✅ (gitflow)
+├── SmartStack.mcp/    ✅ (gitflow)
+├── SmartStack.cli/    ✅ (gitflow)
+└── NewProject/        ← THIS PROJECT
+    ├── .bare/
+    ├── 01-Main/
+    ├── 02-Develop/
+    ├── features/
+    ├── releases/
+    └── hotfixes/
+```
+
+```yaml
+AskUserQuestion:
+  - header: "Location"
+    question: "Root folder for THIS project? (worktrees will be created here)"
+    options:
+      - label: "Use parent folder (Recommended)"
+        description: "{DETECTED_FOLDER}/ - consistent with {#SIBLING_PROJECTS} sibling project(s)"
+      - label: "Use current folder"
+        description: "$(pwd)/ - Will create subfolders here"
+      - label: "Custom path"
+        description: "Specify a different location"
+    multiSelect: false
+```
+
+**⛔ FOLLOW-UP: If user selects "Custom path":**
+
+You MUST ask a follow-up question to get the actual path:
+
+```yaml
+AskUserQuestion:
+  - header: "Path"
+    question: "Enter the full path for the project root folder:"
+    options:
+      - label: "{DETECTED_FOLDER}/"
+        description: "Parent of current directory"
+      - label: "{WORKSPACE_DIR}/"
+        description: "Workspace root"
+    multiSelect: false
+```
+
+The user will type the actual path via "Other". Validate the path exists or can be created.
+
+**Explain the structure that will be created for this project:**
+
+```
+{ROOT_FOLDER}/
+├── .bare/                 # Git bare repository (this repo only)
+├── 01-Main/               # Worktree: main branch
+├── 02-Develop/            # Worktree: develop branch
+├── features/              # Feature branch worktrees
+├── releases/              # Release branch worktrees
+└── hotfixes/              # Hotfix branch worktrees
+```
+
+## Question 3: Project Name
+
+**⛔ ALWAYS ask to confirm project name:**
+
+```yaml
+AskUserQuestion:
+  - header: "Project"
+    question: "Project name? (detected: {DETECTED_NAME})"
+    options:
+      - label: "Use detected name (Recommended)"
+        description: "Project: {DETECTED_NAME}"
+      - label: "Custom name"
+        description: "Specify a different project name"
+    multiSelect: false
+```
+
+**⛔ FOLLOW-UP: If user selects "Custom name":**
+
+You MUST ask a follow-up question to get the actual name:
+
+```yaml
+AskUserQuestion:
+  - header: "Name"
+    question: "Enter the project name:"
+    options:
+      - label: "{DETECTED_NAME}"
+        description: "Detected from repository"
+      - label: "{DETECTED_NAME}-v2"
+        description: "Variant of detected name"
+    multiSelect: false
+```
+
+The user will type the actual name via "Other". Use this raw input for step 6b (normalization).
+
+## Question 4: Existing Configuration
+
+**If `ALREADY_INITIALIZED` = true:**
+
+Display current configuration and ask what to do:
+
+```yaml
+AskUserQuestion:
+  - header: "Existing"
+    question: "GitFlow is already initialized. Current config will be shown. What do you want to do?"
+    options:
+      - label: "Reconfigure (Recommended)"
+        description: "Review and update all settings"
+      - label: "Repair"
+        description: "Fix missing directories only"
+      - label: "View only"
+        description: "Display current config and exit"
+      - label: "Cancel"
+        description: "Exit without changes"
+    multiSelect: false
+```
+
+**Handle choices:**
+- **Reconfigure**: Continue to step 4 (will ask all questions again)
+- **Repair**: Check directories, fix missing ones, exit
+- **View only**: Display config, exit
+- **Cancel**: Exit immediately
+
+## Question 5: Worktree Mode
+
+```yaml
+AskUserQuestion:
+  - header: "Worktrees"
+    question: "How should worktrees be organized?"
+    options:
+      - label: "Organized (Recommended)"
+        description: "01-Main, 02-Develop, features/, releases/, hotfixes/"
+      - label: "Simple"
+        description: "main/, develop/, features/, releases/, hotfixes/"
+      - label: "Disabled"
+        description: "No worktrees, use git checkout (not recommended)"
+    multiSelect: false
+```