Sf Debug

What it does

The Sf Debug skill analyzes Salesforce debug logs to diagnose issues during test runs and identify root causes. It helps users understand governor limit problems, stack traces, slow queries, CPU/heap pressure, and facilitates a reproduction-to-fix loop based on log evidence. This skill is specifically designed for analyzing .log files generated by Salesforce environments.

When to use it

• When you need to determine the root cause of issues identified in Salesforce debug logs.
• For diagnosing governor limit errors.
• To investigate slow queries and performance bottlenecks.
• To analyze CPU or heap pressure within a Salesforce org.
• When attempting to reproduce and fix problems based on evidence found in log files.

Key capabilities

• Analysis of Salesforce debug logs (.log files).
• Interpretation of stack traces and exception analysis.
• Identification of governor limit issues.
• Investigation of SOQL/DML/CPU/heap performance.
• Classification of issue severity (Critical, Warning, Info).
• Recommendation of root-cause oriented fixes that are bulk-safe and testable.

Example prompts

• "Analyze this Salesforce debug log for governor limit issues."
• "Can you identify the cause of this slow query based on the provided log?"
• "What's causing the CPU pressure shown in this Salesforce log file?"

Tips & gotchas

• The skill requires a Salesforce org alias to retrieve logs.
• It is not intended for debugging Apex tests or implementing code fixes; use sf-testing and sf-apex for those tasks respectively.
• To get the most out of this skill, provide an approximate timestamp or transaction window related to the failing event.