Skip to content
Agentmart
Submit a tool

apex-test-debugging

Run and debug Salesforce Apex tests using agent-friendly CLI output.

Skill by Diegod96

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/diegod96-apex-test-debugging

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Run and debug Salesforce Apex tests using agent-friendly CLI output.

Use cases: testing, sales, agent-building

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/apex-test-debugging

What's inside

Skill name
apex-test-debugging
Description
Run and debug Salesforce Apex tests using agent-friendly CLI output.
License
MIT
Instructions
25 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Apex Test Debugging

Use when Apex tests fail, coverage changes, or a deployment validation reports test errors.

## Workflow

1. Identify the target org and exact test scope.
2. Run tests with JSON output:

```bash
sf apex run test --target-org <alias> --test-level RunSpecifiedTests --tests MyClassTest --result-format human --wait 10 --json
```

3. Read failing method names, stack traces, assertion messages, and async job IDs.
4. Reproduce the narrowest failing test before editing code.
5. Fix the behavior or test data setup, then rerun the same test command.
6. Broaden to related classes or `RunLocalTests` when the narrow test passes.

## Guardrails

- Do not chase coverage-only changes without verifying behavior.
- Keep test data self-contained and avoid SeeAllData unless there is a documented platform reason.
- Preserve the original failure evidence in the summary.

From Diegod96/Salesforce-Cursor-Plugin, MIT.

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Apr 25, 2026 (6 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from Diegod96

Cite this page

apex-test-debugging skill. Agent Mart. https://agentmart.dev/skills/diegod96-apex-test-debugging (last updated 2026-10-24)