ai-flow-dev 2.5.1 → 2.5.2

package/prompts/frontend/flow-commit.md

@@ -8,46 +8,112 @@ description: Conventional Commits Automation
 
 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.
+**🚀 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
+
+## 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 4: Summary & Push
+### 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`**

package/prompts/frontend/flow-work-feature.md

@@ -7,42 +7,55 @@ description: Internal logic for Feature implementation within flow-work
 This file contains the detailed execution logic for implementing new features, imported by `@flow-work.md`.
 
 ---
+
 ## 🚀 Feature Implementation Flow
 
 ### 1. Context Analysis (auto-skip if User Story with detailed tasks)
+
 - Extract requirements from User Story or Roadmap
 - If User Story has detailed tasks: Skip to work.md generation
 - If Roadmap or Manual: Analyze and refine
 - Read relevant documentation (ai-instructions.md, architecture.md, etc.)
 
 ### 2. work.md Generation
+
 - Generate consolidated work.md (see Phase 2 in flow-work.md)
 - Include: Context, Objective, Constraints, Approach, Tasks, Validation
 - **User Confirmation Required**
 
 ### 3. Progressive Implementation
+
 Choose mode:
+
 - **Auto**: Complete all tasks without pausing
 - **Phase-by-phase**: Pause and validate after each phase
 - **Task-by-task**: Pause after each task
 
 Follow tasks in `work.md`:
+
 - Update checkboxes as completed
 - Update `status.json` progress
 - Follow patterns and constraints specified
 
 ### 4. Definition of Done (DoD)
+
 - If HU mode: Validate against Gherkin scenarios
 - Run tests and linting
 - Perform security check
 - **Update completion status** in source documents (see Phase 4 in flow-work.md)
 
 ---
+
 ## 🌿 Git Branching Strategy
+
 - Generate slug from name
 - Execute `git checkout -b feature/[slug]`
+- **Note:** Creating feature branches FROM `main`/`master`/`develop`/`development` is correct workflow
+- **Never commit directly TO protected branches** - always work on feature branch
 - Maintain `status.json` with commit history
 
 ---
+
 ## 📦 status.json Persistence
+
 Ensure `progress`, `git`, and `metadata` sections are always updated.

package/prompts/frontend/flow-work-fix.md

@@ -29,7 +29,9 @@ This file contains the detailed execution logic for bug fixes, imported by `@flo
 ---
 ## 🌿 Git Branching Strategy
 - **QUICK**: Usually work on current branch
+  - ⚠️ **Exception:** If on protected branch (`main`, `master`, `develop`, `development`), create fix branch even for quick fixes
 - **COMPLEX**: Execute `git checkout -b fix/[slug]`
+- **Never commit directly TO protected branches**
 
 ---
 ## 📦 status.json Persistence

package/prompts/frontend/flow-work-refactor.md

@@ -7,9 +7,11 @@ description: Internal logic for Refactor implementation within flow-work
 This file contains the detailed execution logic for code refactoring, imported by `@flow-work.md`.
 
 ---
+
 ## 🔄 Refactoring Workflow
 
 ### 1. Scope Identification & work.md Generation
+
 - Map affected files and dependencies
 - Confirm no behavior change expected
 - Validate against architecture patterns
@@ -20,19 +22,27 @@ This file contains the detailed execution logic for code refactoring, imported b
   - "No behavior change" constraint
 
 ### 2. Implementation
+
 - Follow work.md tasks sequentially
 - Update imports and references across codebase
 - **Critical**: Existing tests must pass without modification (unless test itself is refactored)
 
 ### 3. Validation
+
 - Run `/flow-check` to verify no regressions
 - Confirm all tests pass
 - **Update completion status** if refactor was tracked in roadmap/user stories (see Phase 4 in flow-work.md)
 
 ---
+
 ## 🌿 Git Branching Strategy
+
 - Execute `git checkout -b refactor/[slug]`
+- **Note:** Creating refactor branches FROM `main`/`master`/`develop`/`development` is correct
+- **Never commit directly TO protected branches**
 
 ---
+
 ## 📦 status.json Persistence
+
 Track `percentage` of updated occurrences and updated file paths.