platform-apex-logs-debug

Yes, governor limit detection is a core feature of this Apex log analysis. It specifically monitors your SOQL, DML, CPU, and heap limit usage within the debug logs, allowing you to identify potential limit breaches before they impact your Salesforce application.

Yes, it provides agentic fix suggestions for slow SOQL queries and other performance issues found in Apex logs. For example, after detecting a slow query, it can automatically suggest adding a custom index to improve query performance in your Salesforce org.

You need to provide an Apex debug log from your Salesforce environment. Once you invoke the Skill with the log data, it applies its knowledge of the debug log format and common performance bottlenecks to analyze the code execution and suggest optimizations.

Hitting CPU limits often results from expensive operations or inefficient loops in your Apex code. This Skill analyzes your debug logs to locate the exact lines causing high CPU usage, helping you understand the source of the bottleneck and suggesting code fixes to reduce the load.

The Skill focuses strictly on performance tuning and debugging Apex code by analyzing debug logs. It requires a valid debug log to function and applies its reasoning to known performance bottlenecks, meaning it cannot detect issues outside the scope of the provided log data.