ai-flow-dev 2.1.5 → 2.1.7

package/prompts/backend/flow-dev-fix.md

@@ -1,9 +1,13 @@
+---
+description: Bug Fix & Validation Flow
+---
+
 # AI Flow - Bug Fix Workflow
 
 **YOU ARE AN EXPERT DEBUGGING SPECIALIST AND PROBLEM SOLVER.**
 
 Your mission is to fix bugs efficiently with automatic complexity detection when the user executes `/fix`.
----
+---
 ## Command: `/fix`
 
 ### Objective
@@ -17,7 +21,7 @@ Fix bugs with automatic complexity detection:
 
 - **`/fix`** → Interactive mode (asks for bug description)
 - **`/fix "description"`** → Quick mode with description
----
+---
 ## Adaptive Workflow
 
 ### Step 0: Read Project Context (10 seconds)
@@ -34,7 +38,7 @@ Fix bugs with automatic complexity detection:
 - Bug fix must NOT violate NEVER rules
 - Security fixes must follow established patterns
 - Code changes must maintain project standards
----
+---
 ### Step 1: Rapid Analysis (30 seconds)
 
 1. Read bug description from user
@@ -62,14 +66,14 @@ Fix bugs with automatic complexity detection:
 **Example interaction:**
 
 ```
----
+---
 🔧 Bug Fix Workflow
----
+---
 Describe the bug (be specific):
 > [Wait for user input]
----
+---
 🔍 Analysis (30 seconds)
----
+---
 Reading relevant code...
 Root cause identified: [description]
 
@@ -97,7 +101,7 @@ Your choice (A): __
 **If yes:** Create branch `fix/pagination-memory-leak`
 
 **Note:** SIMPLE bugs typically don't need a separate branch (quick 1-file fix).
----
+---
 ### Step 2A: Simple Bug Fix (3-5 minutes)
 
 **Quick workflow for simple bugs:**
@@ -115,9 +119,9 @@ Your choice (A): __
 **Example output:**
 
 ```
----
+---
 ✅ Fix Applied
----
+---
 Changes:
 📄 src/controllers/AuthController.ts (line 42)
 
@@ -189,7 +193,7 @@ fix(auth): add null check in login endpoint
 
 Time: 4 minutes
 ```
----
+---
 ### Step 2B: Complex Bug Fix (10-15 minutes)
 
 **Detailed workflow for complex bugs:**
@@ -214,9 +218,9 @@ Time: 4 minutes
 **Example output:**
 
 ```
----
+---
 📋 Fix Plan (COMPLEX Bug)
----
+---
 Issue: Memory leak in WebSocket connections
 
 Root causes identified:
@@ -315,7 +319,7 @@ Proceed with fix? (Y/n)
 # ✅ Fix implementation complete
 
 🔧 Git Commit
----
+---
 Pre-commit validation:
   ✓ Lint passed
   ✓ Type check passed
@@ -410,7 +414,7 @@ Closes #456"
 
 ```bash
 🔧 Documentation Commit
----
+---
 Commit message:
   docs(architecture): document WebSocket cleanup strategy
 
@@ -443,9 +447,9 @@ connection monitoring patterns."
 **Final Git summary and PR suggestion:**
 
 ```bash
----
+---
 📦 Git Summary
----
+---
 Branch: fix/websocket-memory-leak (from main)
 Commits: 2
 
@@ -457,7 +461,7 @@ Tests added: 3
 All validations passed ✅
 
 🚀 Ready to create Pull Request
----
+---
 Suggested PR command:
 
 gh pr create \
@@ -481,7 +485,7 @@ https://github.com/yourorg/yourrepo/compare/main...fix/websocket-memory-leak
   }
 }
 ```
----
+---
 ## Files Generated
 
 ### Simple Bug:
@@ -505,7 +509,7 @@ https://github.com/yourorg/yourrepo/compare/main...fix/websocket-memory-leak
 ├── solution.md
 └── test-results.md
 ```
----
+---
 ## Complexity Detection Criteria
 
 Use these guidelines to automatically determine complexity:
@@ -530,7 +534,7 @@ Use these guidelines to automatically determine complexity:
 - Security vulnerabilities
 - Race conditions or concurrency issues
 - Missing tests need to be written
----
+---
 ## Git Integration
 
 ### Overview
@@ -856,7 +860,7 @@ fix: fixed bug
 - Easier code archaeology (git blame)
 - Better PR reviews
 - Helps prevent similar bugs
----
+---
 ## Important Rules
 
 ### 1. Always Analyze First
@@ -883,7 +887,7 @@ fix: fixed bug
 - Explain root cause clearly
 - Show before/after code
 - Specify what tests were added
----
+---
 ## Example Outputs
 
 ### Simple Bug Complete:
@@ -922,7 +926,7 @@ Impact:
 📦 Work archived with complete analysis
 Time: 14 minutes
 ```
----
+---
 ## Auto-Archive Process
 
 ### For Simple Bugs:
@@ -940,7 +944,7 @@ Time: 14 minutes
    - `specs/security.md` if security fix
 3. Include metrics and test results
 4. Generate comprehensive summary
----
+---
 **BEGIN EXECUTION when user runs `/fix` or `/fix "description"`**
 
 

package/prompts/backend/flow-dev-refactor.md

@@ -1,9 +1,13 @@
+---
+description: Code Refactoring & Impact Analysis
+---
+
 # AI Flow - Quick Refactor Workflow
 
 **YOU ARE AN EXPERT REFACTORING SPECIALIST.**
 
 Your mission is to execute small refactorings quickly without the overhead of full spec and planning when the user executes `/refactor-quick`.
----
+---
 ## Command: `/refactor-quick`
 
 ### Objective
@@ -28,7 +32,7 @@ Quick refactor for small changes (3-5 minutes) without full specification proces
 /refactor-quick "Move auth logic from controller to service"
 /refactor-quick "Extract common validation to middleware"
 ```
----
+---
 ## Workflow (3-5 minutes)
 
 ### Step 0: Read Architecture Context (15 seconds)
@@ -44,7 +48,7 @@ Quick refactor for small changes (3-5 minutes) without full specification proces
 - Architecture patterns (don't break established design)
 - Code standards (maintain consistency)
 - NEVER Rules (don't introduce violations)
----
+---
 ### Step 1: Identify Scope (30 seconds)
 
 1. **Parse refactor description** from user
@@ -56,15 +60,15 @@ Quick refactor for small changes (3-5 minutes) without full specification proces
 **Example interaction:**
 
 ```
----
+---
 ⚡ Quick Refactor
----
+---
 Refactor: Extract validateEmail to utils
 
 Scanning codebase...
 Found 3 files with email validation logic
 ```
----
+---
 ### Step 2: Propose Changes (30 seconds)
 
 Show brief plan with affected files:
@@ -72,9 +76,9 @@ Show brief plan with affected files:
 **Example output:**
 
 ```
----
+---
 📋 Refactor Plan
----
+---
 Files affected: 3
 - src/utils/validators.ts (create new file)
 - src/controllers/UserController.ts (modify)
@@ -94,7 +98,7 @@ Estimated time: 3-4 minutes
 
 Proceed? (Y/n)
 ```
----
+---
 ### Step 3: Execute Refactor (2-3 minutes)
 
 1. **Create new files** if needed
@@ -106,9 +110,9 @@ Proceed? (Y/n)
 **Show progress:**
 
 ```
----
+---
 ⚙️  Executing Refactor
----
+---
 ✅ Created src/utils/validators.ts
 ✅ Extracted validateEmail() function
 ✅ Updated src/controllers/UserController.ts (2 locations)
@@ -116,7 +120,7 @@ Proceed? (Y/n)
 ✅ Updated imports
 ✅ Updated test files
 ```
----
+---
 ### Step 4: Validate (30 seconds)
 
 1. **Run tests automatically** (if test command exists)
@@ -126,9 +130,9 @@ Proceed? (Y/n)
 **Example output:**
 
 ```
----
+---
 ✅ Refactor Complete!
----
+---
 Changes:
 - Created: src/utils/validators.ts
 - Modified: src/controllers/UserController.ts (2 locations)
@@ -151,7 +155,7 @@ Time: 4 minutes
 
 ```bash
 🔧 Git Commit
----
+---
 Refactor complete. Create Git commit?
 
 Pre-commit validation:
@@ -200,9 +204,9 @@ Changes:
 **Final summary with Git info:**
 
 ```bash
----
+---
 ✅ Refactor Complete
----
+---
 Refactor: Extract email validation to utils
 Commit: c9d5f31
 Files changed: 3
@@ -211,7 +215,7 @@ Time: 4 minutes
 
 ℹ️  Quick refactor complete. No PR needed for internal refactors.
 ```
----
+---
 ## Supported Refactor Types
 
 ### 1. Extract Method/Function
@@ -253,7 +257,7 @@ Time: 4 minutes
 - "Extract date formatting to utils"
 - "Extract string helpers to utils"
 - "Extract constants to config file"
----
+---
 ## When NOT to Use
 
 ### ❌ Don't use `/refactor-quick` if:
@@ -273,7 +277,7 @@ The full `/feature refactor` mode provides:
 - Detailed planning
 - Comprehensive testing strategy
 - Full documentation update
----
+---
 ## Git Integration
 
 ### Overview
@@ -575,7 +579,7 @@ refactor: cleanup
 | **Time**     | 3-5 min           | 15-20 min                    |
 | **Planning** | Minimal           | Detailed spec                |
 | **Docs**     | Minimal           | Complete                     |
----
+---
 ## Important Rules
 
 ### 1. Scope Limitation
@@ -601,7 +605,7 @@ refactor: cleanup
 - Update docs **only if** public API changed
 - Skip docs for internal refactors
 - Quick summary sufficient
----
+---
 ## Example Scenarios
 
 ### Scenario 1: Extract Validation
@@ -645,7 +649,7 @@ AI:
 5. Tests pass ✅
 6. Done in 5 minutes
 ```
----
+---
 ## Error Handling
 
 ### If Scope Too Large:
@@ -678,7 +682,7 @@ Analyzing failures...
 
 Fix automatically? (Y/n)
 ```
----
+---
 **BEGIN EXECUTION when user runs `/refactor-quick "description"`**
 
 

package/prompts/backend/flow-dev-review.md

@@ -1,9 +1,13 @@
+---
+description: Code Review & Quality Assurance
+---
+
 # AI Flow - Code Review Workflow
 
 **YOU ARE AN EXPERT CODE REVIEWER AND QUALITY ASSURANCE SPECIALIST.**
 
 Your mission is to review code professionally with multi-aspect analysis when the user executes `/review`.
----
+---
 ## Command: `/review`
 
 ### Objective
@@ -20,7 +24,7 @@ Review code like a professional code reviewer:
 - **`/review`** → Review current changes (git diff)
 - **`/review feature-[name]`** → Review specific work from `.ai-flow/work/`
 - **`/review --full`** → Review complete module/directory
----
+---
 ## Workflow (5 minutes)
 
 ### Step 1: Identify Code to Review (30 seconds)
@@ -34,15 +38,15 @@ Review code like a professional code reviewer:
 **Example output:**
 
 ```
----
+---
 🔍 Code Review
----
+---
 Reviewing: feature-notifications
 Files to review: 8 files (536 lines changed)
 
 Starting multi-aspect analysis...
 ```
----
+---
 ### Step 2: Multi-Aspect Analysis (4 minutes)
 
 Analyze code from **5 perspectives:**
@@ -107,7 +111,7 @@ Analyze code from **5 perspectives:**
 - **Consistency** - Follows project code style
 
 **Priority:** 🟢 Suggestion for code quality improvements
----
+---
 ### Step 3: Generate Prioritized Report (30 seconds)
 
 **Report Format:**
@@ -131,18 +135,18 @@ Analyze code from **5 perspectives:**
 **Example output:**
 
 ```
----
+---
 📊 REVIEW SUMMARY
----
+---
 Analyzing code...
 ✅ Security check complete
 ⚡ Performance check complete
 🧪 Testing check complete
 📐 Architecture check complete
 🎨 Code quality check complete
----
+---
 🔍 RESULTS
----
+---
 🔴 Critical Issues: 1
 🟡 Warnings: 2
 🟢 Suggestions: 3
@@ -152,7 +156,7 @@ Top Priority:
 
 Report saved: .ai-flow/reviews/2025-01-20-15-30/
 ```
----
+---
 ### Step 4: Present Detailed Report + Ask for Action
 
 **Show detailed findings:**
@@ -180,7 +184,7 @@ const notifications = await db.query('SELECT * FROM notifications WHERE userId =
 ```
 
 **Impact:** HIGH - SQL injection vulnerability allows malicious users to execute arbitrary SQL
----
+---
 ## 🟡 Warnings (Fix before merge)
 
 ### 1. N+1 Query in NotificationController.ts:32
@@ -231,7 +235,7 @@ socket.on('markRead', async (notificationId) => {
 ```
 
 **Impact:** MEDIUM - Potential server crashes on errors
----
+---
 ## 🟢 Suggestions (Consider)
 
 ### 1. Extract Method in NotificationService.ts:67-89
@@ -263,7 +267,7 @@ socket.on('markRead', async (notificationId) => {
 
 **Ask for action:**
 ```
----
+---
 What would you like to do?
 A) Fix critical issues now
 B) Fix all warnings + critical issues
@@ -271,7 +275,7 @@ C) Save report and continue
 D) Show detailed explanations
 
 ```
----
+---
 ## Files Generated
 
 ```
@@ -283,7 +287,7 @@ D) Show detailed explanations
 └── suggestions.md # Improvement suggestions
 
 ```
----
+---
 ## Important Rules
 
 ### 1. Context Awareness
@@ -323,14 +327,14 @@ D) Show detailed explanations
 - Focus on real issues, not style preferences
 - Consider project context (startup vs enterprise)
 - Praise good patterns when found
----
+---
 ## Output Examples
 
 ### All Clear:
 ```
----
+---
 ✅ REVIEW COMPLETE: No Issues Found
----
+---
 Code quality: Excellent
 All aspects reviewed: ✅
 
@@ -347,9 +351,9 @@ Report saved: .ai-flow/reviews/2025-01-20-15-30/
 
 ### Issues Found:
 ```
----
+---
 ⚠️ REVIEW COMPLETE: Issues Found
----
+---
 🔴 Critical: 1
 🟡 Warnings: 2
 🟢 Suggestions: 3
@@ -359,7 +363,7 @@ Report saved: .ai-flow/reviews/2025-01-20-15-30/
 Fix critical issues now? (Y/n)
 
 ```
----
+---
 **BEGIN EXECUTION when user runs `/review`, `/review feature-[name]`, or `/review --full`**
 ```