Can it detect SOQL-in-loop issues?

Yes, it parses log events for repeating SOQL_EXECUTE_BEGIN patterns and identifies the specific class and line number causing the violation.

How does sf-debug access my Salesforce logs?

The skill utilizes the Salesforce CLI (sf) to run commands like 'sf apex list log' and 'sf apex get log' on your behalf to retrieve data from your connected orgs.

Can I use this for real-time log monitoring?

Absolutely, the skill supports log tailing with customizable debug levels to monitor transactions as they happen in your Salesforce environment.

Does it suggest code fixes automatically?

Yes, after identifying a root cause, it provides optimized code snippets and can coordinate with other Salesforce skills to implement the fix.

Salesforce Debugging & Log Analysis

Name: Salesforce Debugging & Log Analysis
Author: Jaganpro

byJaganpro

•

Analytics & Monitoring

Automates Salesforce debug log analysis to identify governor limit issues, performance bottlenecks, and root causes for Apex exceptions.

About

The sf-debug skill transforms Claude into a specialized Salesforce debugging engineer capable of parsing complex Apex debug logs and identifying critical issues like governor limit violations (SOQL, DML, CPU) and non-selective queries. It integrates directly with the Salesforce CLI to retrieve logs, analyze stack traces, and provide actionable recommendations. By interpreting log events and performance hotspots, it suggests agentic code fixes that can be implemented immediately, significantly reducing the time required to troubleshoot production errors and optimize Salesforce application performance.

Key Features

Detailed performance profiling for CPU time hotspots and external callout latency
32 GitHub stars
Detection of governor limit violations including SOQL/DML in loops and heap size limits
Agentic fix suggestions that generate optimized code patterns to resolve identified issues
Automated Apex debug log retrieval and real-time tailing via Salesforce CLI
Intelligent stack trace interpretation and root cause analysis for fatal exceptions

Use Cases

Troubleshooting 'Too many SOQL queries: 101' errors by identifying unbulkified code in loops
Identifying the root cause of NullPointerExceptions in complex, multi-layered trigger frameworks
Optimizing transaction performance by pinpointing expensive algorithms that consume excessive CPU time

About

Key Features

Detailed performance profiling for CPU time hotspots and external callout latency
32 GitHub stars
Detection of governor limit violations including SOQL/DML in loops and heap size limits
Agentic fix suggestions that generate optimized code patterns to resolve identified issues
Automated Apex debug log retrieval and real-time tailing via Salesforce CLI
Intelligent stack trace interpretation and root cause analysis for fatal exceptions

Use Cases

Troubleshooting 'Too many SOQL queries: 101' errors by identifying unbulkified code in loops
Identifying the root cause of NullPointerExceptions in complex, multi-layered trigger frameworks
Optimizing transaction performance by pinpointing expensive algorithms that consume excessive CPU time