sf-debug_skill

Overview

This skill provides Salesforce debug log analysis, governor limit detection, performance bottleneck identification, and automated fix suggestions for Apex, Flows, and integrations. It parses debug logs, interprets stack traces and limit snapshots, and proposes targeted, deployable remediation steps. The skill can integrate with agentic workflows to generate and apply fixes automatically.

How this skill works

It ingests Apex debug logs (fetched via CLI or streamed) and produces an execution overview, governor limit analysis, performance hotspots, and exception root-cause reports. The analyzer detects patterns like SOQL/DML in loops, non-selective queries, high CPU or heap usage, and callout saturation. For each issue it recommends concrete code or configuration changes and can call downstream skills to generate, deploy, and verify fixes.

When to use it

• Investigating test failures, deployment errors, or runtime exceptions
• Diagnosing performance regressions or slow API requests
• Identifying governor limit breaches (SOQL, DML, CPU, heap, callouts)
• Root-cause analysis after a fatal error or transaction rollback
• Automating triage and remediation in CI/CD or monitoring pipelines

Best practices

• Collect relevant logs with transaction or user IDs and time window before analysis
• Use higher debug levels only for targeted sessions to avoid large logs
• Prioritize fixes that address root cause, not just symptoms
• Bulkify operations: move queries/DML out of loops and use Maps
• Verify fixes by re-running the failing transaction and comparing new logs

Example use cases

• Detecting and fixing SOQL queries inside loops during bulk data loads
• Identifying non-selective queries that scan hundreds of thousands of rows
• Finding top CPU consumers and moving heavy work to async jobs
• Resolving NullPointerException stack traces to the exact class and line
• Automating an agentic loop: detect issue → generate fix → deploy → verify