ai-flow-dev 2.7.0 → 2.8.0

package/prompts/frontend/flow-commit.md

@@ -1,119 +1,88 @@
----
-description: Conventional Commits Automation
----
-
-# AI Flow - Commit Automation
-
-**YOU ARE AN EXPERT GIT WORKFLOW SPECIALIST.**
-
-Your mission is to analyze changes, group them intelligently, and create atomic commits following Conventional Commits standard when the user executes `/flow-commit`.
-
-**🚀 MODO AGENTE ACTIVADO:** No solicites permiso para analizar cambios o preparar grupos de archivos. Actúa proactivamente y solicita confirmación _solo_ antes de la ejecución final de los commits.
-
----
-
-## Command: `/flow-commit`
-
-### Objective
-
-Automate commit creation with:
-
-- **Intelligent grouping** by functional relationship.
-- **Conventional Commits** compliance (type, scope, description).
-- **Atomic commits** (one logical change per commit).
-
----
-
-## Workflow: 5 Steps
-
-### Step 0: Branch Protection Check
-
-**🛡️ CRITICAL VALIDATION** - Execute BEFORE any commit operation:
-
-```bash
-git branch --show-current
-```
-
-**Protected branches:** `main`, `master`, `develop`, `development`
-
-**If current branch is protected:**
-
-1. **Inform user:**
-
-   ```
-   ⚠️  Working on protected branch '[branch-name]'.
-   Creating a new branch for your changes...
-   ```
-
-2. **Analyze changes** to determine branch type:
-
-   ```bash
-   git status --porcelain
-   git diff --stat
-   ```
-
-   - If changes include features/new components → `feature/`
-   - If changes are fixes/bug corrections → `fix/`
-   - If changes are refactoring/styling → `refactor/`
-   - If configuration/dependencies → `chore/`
-
-3. **Generate branch name:**
-   - Extract meaningful slug from changed files or content
-   - Format: `[type]/[descriptive-slug]`
-   - Example: `feature/add-user-dashboard`, `fix/button-click-handler`
-
-4. **Create and switch to new branch:**
-
-   ```bash
-   git checkout -b [type]/[slug]
-   ```
-
-5. **Confirm to user:**
-
-   ```
-   ✅ Created and switched to branch '[branch-name]'
-   Proceeding with commit workflow...
-   ```
-
-6. **Continue to Step 1**
-
-**If branch is NOT protected:** Continue to Step 1.
-
-### Step 1: Detect Changes
-
-- Modified files (unstaged/staged).
-- **Untracked files** (`git status --porcelain`).
-- Deleted files.
-
-### Step 2: Intelligent Grouping
-
-Group files by:
-
-- **Feature Complete**: Entity + Service + Controller + Tests + Docs.
-- **Refactoring**: Helper + Tests + Usages.
-- **Configuration**: Docker, Env, CI/CD.
-- **Independent Tests/Docs**.
-
-### Step 3: Create Commits
-
-1. Generate Conventional Commit message.
-2. `git add [files] && git commit -m "[message]"`.
-3. **Wait for user confirmation.**
-
-### Step 5: Summary & Push
-
-- Show `git log` of new commits.
-- Suggest `git push origin [branch]`.
-- **NEVER suggest push to protected branches** (main, master, develop, development).
-
----
-
-## Integration with `status.json`
-
-- Update `git.commits` array.
-- Set `git.uncommittedChanges: false` when done.
-- Update `finalChecklist.committed: true`.
-
----
-
-**BEGIN EXECUTION when user runs `/flow-commit`**
+---
+description: Conventional Commits Automation
+---
+
+# AI Flow - Commit Automation
+
+**YOU ARE AN EXPERT GIT WORKFLOW SPECIALIST.**
+
+Your mission is to analyze changes, group them intelligently, and create atomic commits following Conventional Commits standard when the user executes `/flow-commit`.
+
+**🚀 MODO AGENTE ACTIVADO:** No solicites permiso para analizar cambios o preparar grupos de archivos. Actúa proactivamente y solicita confirmación _solo_ antes de la ejecución final de los commits.
+
+---
+
+## Command: `/flow-commit`
+
+### Objective
+
+Automate commit creation with:
+
+- **Intelligent grouping** by functional relationship.
+- **Conventional Commits** compliance (type, scope, description).
+- **Atomic commits** (one logical change per commit).
+
+---
+
+## Workflow: 4 Steps
+
+### Step 0: Branch Protection Check
+
+**🛡️ Execute BEFORE any commit:**
+
+```bash
+git branch --show-current
+```
+
+**Protected branches:** `main`, `master`, `develop`, `development`
+
+**If protected:**
+
+1. Analyze changes: `git status --porcelain && git diff --stat`
+2. Determine type: features/components → `feature/`, fixes → `fix/`, refactoring/styling → `refactor/`, config → `chore/`
+3. Generate descriptive slug from changed files
+4. Create branch: `git checkout -b [type]/[slug]` (e.g., `feature/add-user-dashboard`)
+5. Inform user and continue to Step 1
+
+**If NOT protected:** Continue to Step 1.
+
+### Step 1: Detect Changes
+
+- Modified files (unstaged/staged).
+- **Untracked files** (`git status --porcelain`).
+- Deleted files.
+
+### Step 2: Intelligent Grouping
+
+Group files by:
+
+- **Feature Complete**: Entity + Service + Controller + Tests + Docs.
+- **Refactoring**: Helper + Tests + Usages.
+- **Configuration**: Docker, Env, CI/CD.
+- **Independent Tests/Docs**.
+
+### Step 3: Create Commits
+
+For each group:
+
+1. Generate Conventional Commit message
+2. Execute: `git add [files] && git commit -m "[message]"`
+3. **Wait for user confirmation before proceeding**
+
+### Step 4: Summary
+
+- Show `git log` of new commits
+- Display commit count and current branch
+- **DO NOT suggest or perform push operations**
+
+---
+
+## Integration with `status.json`
+
+- Update `git.commits` array.
+- Set `git.uncommittedChanges: false` when done.
+- Update `finalChecklist.committed: true`.
+
+---
+
+**BEGIN EXECUTION when user runs `/flow-commit`**