Maintenance: Enhances SFCC debugging workflows

Streamlines the debugging process for SFCC development by prioritizing essential log checks and refining the sequence of steps.

This update removes redundant steps and incorporates checks for warnings and debug-level messages.

Author: taurgis

ai-instructions/cursor/.cursor/rules/debugging-workflows.mdc

@@ -23,8 +23,7 @@ Use this rule when investigating errors, performance issues, or debugging SFCC a
 
 ### 🔍 For Transaction Tracing:
 1. `mcp_sfcc-dev_search_logs` with pattern: [transaction-id] - Find transaction entries
-2. `mcp_sfcc-dev_get_related_logs` with correlationId: [transaction-id] - Get complete flow
-3. `mcp_sfcc-dev_search_logs` with pattern: [customer-id] - Track customer journey
+2. `mcp_sfcc-dev_search_logs` with pattern: [customer-id] - Track customer journey
 
 ### 📊 For System Health Assessment:
 1. `mcp_sfcc-dev_summarize_logs` - Overall system status
@@ -76,19 +75,7 @@ Use: mcp_sfcc-dev_get_latest_error (limit: 5)
 Purpose: Identify most recent critical issues
 ```
 
-**Step 3: Pattern Analysis**
-```
-Use: mcp_sfcc-dev_analyze_error_patterns with errorMessage: [specific error]
-Purpose: Get intelligent diagnosis with SFCC-specific solutions
-```
-
-**Step 4: Transaction Tracing**
-```
-Use: mcp_sfcc-dev_get_related_logs with correlationId: [id]
-Purpose: Follow complete request/transaction flow
-```
-
-**Step 5: Best Practice Consultation**
+**Step 3: Best Practice Consultation**
 ```
 Use: mcp_sfcc-dev_search_best_practices with query: [relevant topic]
 Purpose: Get SFCC-specific debugging and fix patterns

ai-instructions/cursor/.cursor/rules/sfcc-development.mdc

@@ -35,9 +35,11 @@ You are a **Senior Salesforce B2C Commerce Cloud Developer** working with the SF
 ### 🐛 Debugging and Troubleshooting Phase:
 1. `mcp_sfcc-dev_summarize_logs` - Get system health overview FIRST
 2. `mcp_sfcc-dev_get_latest_error` - Check recent critical errors
-3. `mcp_sfcc-dev_search_logs` - Search for specific error patterns
-4. `mcp_sfcc-dev_analyze_error_patterns` - Deep analysis of recurring issues
-5. `mcp_sfcc-dev_get_related_logs` - Trace specific transactions
+3. `mcp_sfcc-dev_get_latest_warn` - Check recent warnings
+4. `mcp_sfcc-dev_get_latest_info` - Check info-level messages
+5. `mcp_sfcc-dev_get_latest_debug` - Check debug-level messages
+6. `mcp_sfcc-dev_search_logs` - Search for specific error patterns
+7. `mcp_sfcc-dev_list_log_files` - List available log files
 
 ### 🎯 Configuration and Setup Phase:
 1. `mcp_sfcc-dev_search_system_object_attribute_groups` - Find preference groups

ai-instructions/github-copilot/copilot-instructions.md

@@ -183,7 +183,7 @@ Use these for debugging and troubleshooting:
    → summarize_logs
 
 2. Check recent errors:
-   → get_latest_errors
+   → get_latest_error
 
 3. Search for specific issues:
    → search_logs with pattern: "your_error_pattern"
@@ -272,11 +272,9 @@ Problem/Error Scenario
 │   ├── → summarize_logs (get system health overview)
 │   ├── → get_latest_error (check recent errors)
 │   └── → search_logs (pattern: error keywords)
-├── "Performance issues"
-│   ├── → get_latest_warn (check warnings)
-│   └── → search_best_practices (query: "performance")
-└── "Need to understand error patterns"
-    └── → analyze_error_patterns (errorMessage: specific error)
+└── "Performance issues"
+    ├── → get_latest_warn (check warnings)
+    └── → search_best_practices (query: "performance")
 ```
 
 #### **When User Asks About Data Models/Objects**
@@ -368,11 +366,6 @@ searchRequest: {
 ```markdown
 For Transaction Tracing:
 1. → search_logs (pattern: "transaction-id-123", logLevel: "info")
-2. → get_related_logs (correlationId: "transaction-id-123", timeWindow: "15min")
-
-For Error Pattern Analysis:
-1. → search_logs (pattern: "NullPointerException", logLevel: "error")
-2. → analyze_error_patterns (errorMessage: "NullPointerException in CartModel", timeRange: "1day")
 
 For Performance Investigation:
 1. → search_logs (pattern: "timeout", logLevel: "warn")
@@ -396,7 +389,7 @@ For Performance Investigation:
 3. **Deep Dive with Detail Tools**
    - get_sfcc_class_documentation
    - search_best_practices
-   - get_related_logs
+   - search_logs
 ```
 
 #### **Parallel vs Sequential Tool Usage**