platform-apex-logs-debug: 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 platform-apex-logs-debug when the work involves:
.log files 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:
Required Context to Gather First
Ask for or infer:
- org alias
- failing transaction / user flow / test name
- approximate timestamp or transaction window
- user / record / request ID if known
- whether the goal is diagnosis only or diagnosis + fix loop
Recommended Workflow
1. Retrieve logs
Use the commands in references/cli-commands.md to list, download, or stream logs for the target org.
2. Analyze in this order
- entry point and transaction type
- exceptions / fatal errors
- governor limits
- repeated SOQL / DML patterns
- CPU / heap hotspots
- callout timing and external failures
3. Classify severity
- Critical — runtime failure, hard limit, corruption risk
- Warning — near-limit, non-selective query, slow path
- Info — optimization opportunity or hygiene issue
4. Recommend the smallest correct fix
Prefer fixes that are:
- root-cause oriented
- bulk-safe
- testable
- easy to verify with a rerun
Expanded workflow: references/analysis-playbook.md
High-Signal Issue Patterns
| Issue |
Primary signal |
Default fix direction |
| SOQL in loop |
repeating SOQL_EXECUTE_BEGIN in a repeated call path |
query once, use maps / grouped collections |
| DML in loop |
repeated DML_BEGIN patterns |
collect rows, bulk DML once |
| Non-selective query |
high rows scanned / poor selectivity |
add indexed filters, reduce scope |
| CPU pressure |
CPU usage approaching sync limit |
reduce algorithmic complexity, cache, async where valid |
| Heap pressure |
heap usage approaching sync limit |
stream with SOQL for-loops, reduce in-memory data |
| Null pointer / fatal error |
EXCEPTION_THROWN / FATAL_ERROR |
guard null assumptions, fix empty-query handling |
Expanded examples: references/common-issues.md
Output Format
When finishing analysis, report in this order:
- What failed
- Where it failed (class / method / line / transaction stage)
- Why it failed (root cause, not just symptom)
- How severe it is
- Recommended fix
- Verification step
Suggested shape:
Issue: <summary>
Location: <class / line / transaction>
Root cause: <explanation>
Severity: Critical | Warning | Info
Fix: <specific action>
Verify: <test or rerun step>
Rules / Constraints
| Rule |
Rationale |
| Always base fix recommendations on log evidence |
Avoid speculative diagnosis — root cause must be traceable in the log |
| Report all six output fields for every issue found |
Ensures actionable, complete findings for each problem |
| Classify every finding as Critical, Warning, or Info |
Helps the user prioritize which issues to address first |
Delegate code generation to platform-apex-generate |
This skill diagnoses; it does not rewrite Apex code |
Delegate test execution to platform-apex-test-run |
This skill does not run or repair test classes |
Never assume limits are safe without reading LIMIT_USAGE events |
Limits may be consumed by earlier operations not visible in the failure point |
Gotchas
| Pitfall |
Resolution |
| Log truncated at 2 MB |
Reduce debug levels (e.g., ApexCode: INFO, ApexProfiling: FINE) and re-capture |
| Same issue appears as both SOQL and CPU problem |
Fix SOQL-in-loop first — it typically drives the CPU spike as a secondary effect |
| No logs appear after trace flag is set |
Verify the trace flag ExpirationDate is in the future and the correct user is traced |
| Async context changes limit values |
CPU limit is 60,000 ms async vs 10,000 ms sync — check transaction type before flagging limits |
| Stack trace points to framework line, not user code |
Walk up the call stack past trigger handlers to find the originating user code |
Cross-Skill Integration
Reference File Index
| File |
When to read |
references/analysis-playbook.md |
Start here — expanded step-by-step workflow for any debugging session |
references/common-issues.md |
Quick lookup for SOQL in loop, DML in loop, CPU/heap pressure, null pointer patterns |
references/cli-commands.md |
SF CLI commands for retrieving, streaming, and managing debug logs |
references/debug-log-reference.md |
Full event type catalog, log levels, and governor limit reference values |
references/log-analysis-tools.md |
Tool guide: Apex Log Analyzer, Developer Console, CLI grep patterns |
references/benchmarking-guide.md |
Performance benchmarking techniques, benchmark data, and anti-patterns |
references/scoring-rubric.md |
100-point scoring rubric for evaluating analysis quality |
assets/benchmarking-template.cls |
Copy-paste Anonymous Apex template for running performance benchmarks |
assets/cpu-heap-optimization.cls |
Apex patterns for reducing CPU time and heap allocation |
assets/dml-in-loop-fix.cls |
Before/after example for resolving DML-in-loop violations |
assets/soql-in-loop-fix.cls |
Before/after example for resolving SOQL-in-loop violations |
assets/null-pointer-fix.cls |
Patterns for guarding against null pointer exceptions |
Score Guide
| Score |
Meaning |
| 90+ |
Expert analysis with strong fix guidance |
| 80–89 |
Good analysis with minor gaps |
| 70–79 |
Acceptable but may miss secondary issues |
| 60–69 |
Partial diagnosis only |
| < 60 |
Incomplete analysis |
1---2name: platform-apex-logs-debug3description: 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 platform-apex-test-run), generating or fixing Apex code (use platform-apex-generate), or Agentforce session tracing (use agentforce-observe).4---56# platform-apex-logs-debug: Salesforce Debug Log Analysis & Troubleshooting78Use 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.910## When This Skill Owns the Task1112Use `platform-apex-logs-debug` when the work involves:13- `.log` files from Salesforce14- stack traces and exception analysis15- governor limits16- SOQL / DML / CPU / heap troubleshooting17- query-plan or performance evidence extracted from logs1819Delegate elsewhere when the user is:20- running or repairing Apex tests → [platform-apex-test-run](../platform-apex-test-run/SKILL.md)21- generating or implementing the code fix → [platform-apex-generate](../platform-apex-generate/SKILL.md)22- debugging Agentforce session traces / parquet telemetry → [agentforce-observe](../agentforce-observe/SKILL.md)2324---2526## Required Context to Gather First2728Ask for or infer:29- org alias30- failing transaction / user flow / test name31- approximate timestamp or transaction window32- user / record / request ID if known33- whether the goal is diagnosis only or diagnosis + fix loop3435---3637## Recommended Workflow3839### 1. Retrieve logs4041Use the commands in [references/cli-commands.md](references/cli-commands.md) to list, download, or stream logs for the target org.4243### 2. Analyze in this order441. entry point and transaction type452. exceptions / fatal errors463. governor limits474. repeated SOQL / DML patterns485. CPU / heap hotspots496. callout timing and external failures5051### 3. Classify severity52- **Critical** — runtime failure, hard limit, corruption risk53- **Warning** — near-limit, non-selective query, slow path54- **Info** — optimization opportunity or hygiene issue5556### 4. Recommend the smallest correct fix57Prefer fixes that are:58- root-cause oriented59- bulk-safe60- testable61- easy to verify with a rerun6263Expanded workflow: [references/analysis-playbook.md](references/analysis-playbook.md)6465---6667## High-Signal Issue Patterns6869| Issue | Primary signal | Default fix direction |70|---|---|---|71| SOQL in loop | repeating `SOQL_EXECUTE_BEGIN` in a repeated call path | query once, use maps / grouped collections |72| DML in loop | repeated `DML_BEGIN` patterns | collect rows, bulk DML once |73| Non-selective query | high rows scanned / poor selectivity | add indexed filters, reduce scope |74| CPU pressure | CPU usage approaching sync limit | reduce algorithmic complexity, cache, async where valid |75| Heap pressure | heap usage approaching sync limit | stream with SOQL for-loops, reduce in-memory data |76| Null pointer / fatal error | `EXCEPTION_THROWN` / `FATAL_ERROR` | guard null assumptions, fix empty-query handling |7778Expanded examples: [references/common-issues.md](references/common-issues.md)7980---8182## Output Format8384When finishing analysis, report in this order:85861. **What failed**872. **Where it failed** (class / method / line / transaction stage)883. **Why it failed** (root cause, not just symptom)894. **How severe it is**905. **Recommended fix**916. **Verification step**9293Suggested shape:9495```text96Issue: <summary>97Location: <class / line / transaction>98Root cause: <explanation>99Severity: Critical | Warning | Info100Fix: <specific action>101Verify: <test or rerun step>102```103104---105106## Rules / Constraints107108| Rule | Rationale |109|------|-----------|110| Always base fix recommendations on log evidence | Avoid speculative diagnosis — root cause must be traceable in the log |111| Report all six output fields for every issue found | Ensures actionable, complete findings for each problem |112| Classify every finding as Critical, Warning, or Info | Helps the user prioritize which issues to address first |113| Delegate code generation to `platform-apex-generate` | This skill diagnoses; it does not rewrite Apex code |114| Delegate test execution to `platform-apex-test-run` | This skill does not run or repair test classes |115| Never assume limits are safe without reading `LIMIT_USAGE` events | Limits may be consumed by earlier operations not visible in the failure point |116117---118119## Gotchas120121| Pitfall | Resolution |122|---------|------------|123| Log truncated at 2 MB | Reduce debug levels (e.g., `ApexCode: INFO`, `ApexProfiling: FINE`) and re-capture |124| Same issue appears as both SOQL and CPU problem | Fix SOQL-in-loop first — it typically drives the CPU spike as a secondary effect |125| No logs appear after trace flag is set | Verify the trace flag `ExpirationDate` is in the future and the correct user is traced |126| Async context changes limit values | CPU limit is 60,000 ms async vs 10,000 ms sync — check transaction type before flagging limits |127| Stack trace points to framework line, not user code | Walk up the call stack past trigger handlers to find the originating user code |128129---130131## Cross-Skill Integration132133| Need | Delegate to | Reason |134|---|---|---|135| Implement Apex fix | [platform-apex-generate](../platform-apex-generate/SKILL.md) | code change generation / review |136| Reproduce via tests | [platform-apex-test-run](../platform-apex-test-run/SKILL.md) | test execution and coverage loop |137| Deploy fix | [platform-metadata-deploy](../platform-metadata-deploy/SKILL.md) | deployment orchestration |138| Create debugging data | [platform-data-manage](../platform-data-manage/SKILL.md) | targeted seed / repro data |139140---141142## Reference File Index143144| File | When to read |145|------|-------------|146| `references/analysis-playbook.md` | Start here — expanded step-by-step workflow for any debugging session |147| `references/common-issues.md` | Quick lookup for SOQL in loop, DML in loop, CPU/heap pressure, null pointer patterns |148| `references/cli-commands.md` | SF CLI commands for retrieving, streaming, and managing debug logs |149| `references/debug-log-reference.md` | Full event type catalog, log levels, and governor limit reference values |150| `references/log-analysis-tools.md` | Tool guide: Apex Log Analyzer, Developer Console, CLI grep patterns |151| `references/benchmarking-guide.md` | Performance benchmarking techniques, benchmark data, and anti-patterns |152| `references/scoring-rubric.md` | 100-point scoring rubric for evaluating analysis quality |153| `assets/benchmarking-template.cls` | Copy-paste Anonymous Apex template for running performance benchmarks |154| `assets/cpu-heap-optimization.cls` | Apex patterns for reducing CPU time and heap allocation |155| `assets/dml-in-loop-fix.cls` | Before/after example for resolving DML-in-loop violations |156| `assets/soql-in-loop-fix.cls` | Before/after example for resolving SOQL-in-loop violations |157| `assets/null-pointer-fix.cls` | Patterns for guarding against null pointer exceptions |158159---160161## Score Guide162163| Score | Meaning |164|---|---|165| 90+ | Expert analysis with strong fix guidance |166| 80–89 | Good analysis with minor gaps |167| 70–79 | Acceptable but may miss secondary issues |168| 60–69 | Partial diagnosis only |169| < 60 | Incomplete analysis |
om-scogo