debugging-apex-logs
PopularSalesforce debug log analysis and troubleshooting with 100-point scoring. TRIGGER when: user analyzes debug logs, hits governor limits, reads stack traces, or touches .log files from Salesforce orgs. DO NOT TRIGGER when: running Apex tests (use running-apex-tests), generating or fixing Apex code (use generating-apex), or Agentforce session tracing (use observing-agentforce).
Salesforce debug log analysis and troubleshooting with 100-point scoring. TRIGGER when: user analyzes debug logs, hits governor limits, reads stack traces, or touches .log files from Salesforce orgs. DO NOT TRIGGER when: running Apex tests (use running-apex-tests), generating or fixing Apex code (use generating-apex), or Agentforce session tracing (use observing-agentforce).
debugging-apex-logs: Salesforce Debug Log Analysis & Troubleshooting
Use this skill when the user needs root-cause analysis from debug logs: governor-limit diagnosis, stack-trace interpretation, slow-query investigation, heap / CPU pressure analysis, or a reproduction-to-fix loop based on log evidence.
When This Skill Owns the Task
Use debugging-apex-logs when the work involves:
-
.logfiles from Salesforce -
stack traces and exception analysis
-
governor limits
-
SOQL / DML / CPU / heap troubleshooting
-
query-plan or performance evidence extracted from logs
Delegate elsewhere when the user is:
-
running or repairing Apex tests → running-apex-tests
-
generating or implementing the code fix → generating-apex
-
debugging Agentforce session traces / parquet telemetry → observing-agentforce
