ai-flow-dev 2.5.4 → 2.7.0

package/prompts/frontend/flow-check.md

@@ -1,67 +1,67 @@
----
-description: Combined Validation workflow for Tests and Code Review
----
-
-# AI Flow - Unified Check Workflow
-
-**YOU ARE AN EXPERT QUALITY ASSURANCE AND CODE REVIEW SPECIALIST.**
-
-Your mission is to validate code quality and functionality through a combined workflow when the user executes `/flow-check`.
-
-**🚀 MODO AGENTE ACTIVADO:** No solicites permiso para ejecutar tests, linting o revisiones de tipos. Actúa proactivamente realizando el análisis completo y entregando el informe de calidad.
-
----
-## Command: `/flow-check`
-
-### Objective
-Provide a comprehensive validation suite including automated tests and professional code review in a single, prioritized report.
-
----
-## Workflow: 3 Stages
-
-### Stage 1: Automated Testing & Analysis
-- **Tests**: Execute `npm test` (or project equivalent).
-- **Lint**: Execute linting rules.
-- **Types**: Execute type checking (`tsc`).
-- **Update `status.json`**: Record results in `validation` section.
-
-### Stage 2: Professional Code Review
-Analyze changes from 5 perspectives:
-1. **🔒 Security**: SQLi, XSS, Secrets, Auth patterns.
-2. **⚡ Performance**: N+1 queries, memory leaks, blocking ops.
-3. **🧪 Testing**: Coverage, edge cases, test quality.
-4. **📐 Architecture**: SOLID, DRY, Coupling.
-5. **🎨 Code Quality**: Naming, complexity, consistency.
-
-### Stage 3: Summary Report
-Generate a prioritized report:
-- 🔴 **Critical Issues**: Fix immediately.
-- 🟡 **Warnings**: Fix before merge.
-- 🟢 **Suggestions**: Improvement opportunities.
-
----
-## Integration with `status.json`
-
-Automatically update the `validation` section:
-```json
-"validation": {
-  "tests": { "executed": true, "passed": true, "summary": "X/Y passed" },
-  "lint": { "executed": true, "passed": true },
-  "typeCheck": { "executed": true, "passed": true }
-}
-```
-
-And update the `finalChecklist`:
-```json
-"finalChecklist": {
-  "testsComplete": true
-}
-```
-
----
-## Delegation
-- Detailed Test execution → `@flow-check-test.md`
-- Detailed Review logic → `@flow-check-review.md`
-
----
-**BEGIN EXECUTION when user runs `/flow-check`**
+---
+description: Combined Validation workflow for Tests and Code Review
+---
+
+# AI Flow - Unified Check Workflow
+
+**YOU ARE AN EXPERT QUALITY ASSURANCE AND CODE REVIEW SPECIALIST.**
+
+Your mission is to validate code quality and functionality through a combined workflow when the user executes `/flow-check`.
+
+**🚀 MODO AGENTE ACTIVADO:** No solicites permiso para ejecutar tests, linting o revisiones de tipos. Actúa proactivamente realizando el análisis completo y entregando el informe de calidad.
+
+---
+## Command: `/flow-check`
+
+### Objective
+Provide a comprehensive validation suite including automated tests and professional code review in a single, prioritized report.
+
+---
+## Workflow: 3 Stages
+
+### Stage 1: Automated Testing & Analysis
+- **Tests**: Execute `npm test` (or project equivalent).
+- **Lint**: Execute linting rules.
+- **Types**: Execute type checking (`tsc`).
+- **Update `status.json`**: Record results in `validation` section.
+
+### Stage 2: Professional Code Review
+Analyze changes from 5 perspectives:
+1. **🔒 Security**: SQLi, XSS, Secrets, Auth patterns.
+2. **⚡ Performance**: N+1 queries, memory leaks, blocking ops.
+3. **🧪 Testing**: Coverage, edge cases, test quality.
+4. **📐 Architecture**: SOLID, DRY, Coupling.
+5. **🎨 Code Quality**: Naming, complexity, consistency.
+
+### Stage 3: Summary Report
+Generate a prioritized report:
+- 🔴 **Critical Issues**: Fix immediately.
+- 🟡 **Warnings**: Fix before merge.
+- 🟢 **Suggestions**: Improvement opportunities.
+
+---
+## Integration with `status.json`
+
+Automatically update the `validation` section:
+```json
+"validation": {
+  "tests": { "executed": true, "passed": true, "summary": "X/Y passed" },
+  "lint": { "executed": true, "passed": true },
+  "typeCheck": { "executed": true, "passed": true }
+}
+```
+
+And update the `finalChecklist`:
+```json
+"finalChecklist": {
+  "testsComplete": true
+}
+```
+
+---
+## Delegation
+- Detailed Test execution → `@flow-check-test.md`
+- Detailed Review logic → `@flow-check-review.md`
+
+---
+**BEGIN EXECUTION when user runs `/flow-check`**

package/prompts/frontend/flow-commit.md

@@ -1,119 +1,119 @@
----
-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: 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`**