Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
jaganpro avatar

Sf Debug

  • 1.4k installs
  • 423 repo stars
  • Updated April 27, 2026
  • jaganpro/sf-skills

sf-debug is an agent skill that apply sf-debug agent skill workflows from documented skill.md guidance.

About

sf-debug is an agent skill from jaganpro/sf-skills that apply sf-debug agent skill workflows from documented skill.md guidance. # sf-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 `sf-debug` Developers invoke sf-debug during ship/testing work for testing & qa tasks. The skill documents triggers, prerequisites, and step-by-step workflows grounded in SKILL.md. Compatible with Claude Code, Cursor, and Codex agent runtimes that load marketplace skills. Review the Security Audits panel on this listing before installing in production environments. Category Testing & QA with development vertical focus supports repeatable agent-guided delivery.

  • sf-debug: Salesforce Debug Log Analysis & Troubleshooting
  • When This Skill Owns the Task
  • Use `sf-debug` when the work involves:
  • `.log` files from Salesforce
  • stack traces and exception analysis

Sf Debug by the numbers

  • 1,383 all-time installs (skills.sh)
  • +4 installs in the week ending Aug 5, 2026 (Skillselion tracking)
  • Ranked #497 of 2,153 Testing & QA skills by installs in the Skillselion catalog
  • Security screen: HIGH risk (skills.sh audit)
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

sf-debug capabilities & compatibility

Capabilities
sf debug: salesforce debug log analysis & troubl · when this skill owns the task · use `sf debug` when the work involves: · `.log` files from salesforce · stack traces and exception analysis
Use cases
orchestration
From the docs

What sf-debug says it does

- SOQL / DML / CPU / heap troubleshooting
SKILL.md
- query-plan or performance evidence extracted from logs
SKILL.md
- running or repairing Apex tests → [sf-testing](../sf-testing/SKILL.md)
SKILL.md
npx skills add https://github.com/jaganpro/sf-skills --skill sf-debug

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1.4k
repo stars423
Security audit3 / 3 scanners passed
Last updatedApril 27, 2026
Repositoryjaganpro/sf-skills

What it does

Apply sf-debug agent skill workflows from documented SKILL.md guidance.

Who is it for?

Developers working on testing & qa during ship tasks.

Skip if: Tasks outside Testing & QA scope described in SKILL.md.

When should I use this skill?

Apply sf-debug agent skill workflows from documented SKILL.md guidance.

What you get

Completed testing & qa workflow aligned with SKILL.md steps.

  • Anonymous Apex benchmark script
  • Performance comparison results

Files

SKILL.mdMarkdownGitHub ↗

sf-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 sf-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:

  • running or repairing Apex tests → sf-testing
  • implementing the code fix → sf-apex
  • debugging Agentforce session traces / parquet telemetry → sf-ai-agentforce-observability

---

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

sf apex list log --target-org <alias> --json
sf apex get log --log-id <id> --target-org <alias>
sf apex tail log --target-org <alias> --color

2. Analyze in this order

1. entry point and transaction type 2. exceptions / fatal errors 3. governor limits 4. repeated SOQL / DML patterns 5. CPU / heap hotspots 6. 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

IssuePrimary signalDefault fix direction
SOQL in looprepeating SOQL_EXECUTE_BEGIN in a repeated call pathquery once, use maps / grouped collections
DML in looprepeated DML_BEGIN patternscollect rows, bulk DML once
Non-selective queryhigh rows scanned / poor selectivityadd indexed filters, reduce scope
CPU pressureCPU usage approaching sync limitreduce algorithmic complexity, cache, async where valid
Heap pressureheap usage approaching sync limitstream with SOQL for-loops, reduce in-memory data
Null pointer / fatal errorEXCEPTION_THROWN / FATAL_ERRORguard null assumptions, fix empty-query handling

Expanded examples: references/common-issues.md

---

Output Format

When finishing analysis, report in this order:

1. What failed 2. Where it failed (class / method / line / transaction stage) 3. Why it failed (root cause, not just symptom) 4. How severe it is 5. Recommended fix 6. 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>

---

Cross-Skill Integration

NeedDelegate toReason
Implement Apex fixsf-apexcode change generation / review
Reproduce via testssf-testingtest execution and coverage loop
Deploy fixsf-deploydeployment orchestration
Create debugging datasf-datatargeted seed / repro data

---

Reference Map

Start here

  • references/analysis-playbook.md
  • references/common-issues.md
  • references/cli-commands.md

Deep references

  • references/debug-log-reference.md
  • references/log-analysis-tools.md
  • references/benchmarking-guide.md

Rubric

  • references/scoring-rubric.md

---

Score Guide

ScoreMeaning
90+Expert analysis with strong fix guidance
80–89Good analysis with minor gaps
70–79Acceptable but may miss secondary issues
60–69Partial diagnosis only
< 60Incomplete analysis

Related skills

Forks & variants (1)

Sf Debug has 1 known copy in the catalog totaling 34 installs. They canonicalize to this original listing.

How it compares

Use this for repeatable Anonymous Apex micro-benchmarks; use Salesforce debug logs or APM tools for production trace analysis.

FAQ

What does sf-debug do?

Apply sf-debug agent skill workflows from documented SKILL.md guidance.

When should I use sf-debug?

During ship testing work for testing & qa.

Is sf-debug safe to install?

Review the Security Audits panel on this listing before production use.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.