Menu
Provides Apex development workflow including static analysis and testing steps. Use before writing Apex classes or triggers
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Merge the base branch into the current branch. Do the merge and resolve the safe parts first, then let a cheap signal decide how deep to look. Go past textual conflicts to semantic breaks, and past those to design consistency. When the base carries a refactor or redesign, bring the current branch into line with it (with the user's consent).
Access Salesforce Apex classes and schema objects. Use BEFORE writing Apex code to check what frameworks, utilities, or patterns are already available (e.g., trigger frameworks, selector patterns, service classes). Also use when you need to know object fields, System class methods, API signatures. Check this when asked to create triggers, services, or any new Apex to see if there's an existing framework to follow.
Use before writing Lightning Web Components.
Gets Claude to think about what went well and badly in a session with an eye on future improvements or lessons for the user.
Based on SOC occupation classification
| name | salesforce-apex |
| description | Provides Apex development workflow including static analysis and testing steps. Use before writing Apex classes or triggers |
| allowed-tools | mcp__ide__getDiagnostics, Bash(sf project deploy *), Bash(sf apex run test *) |
Read project config โ Get sourceApiVersion from sfdx-project.json for all new -meta.xml files.
Write the Apex code
Check IDE diagnostics โ Use mcp__ide__getDiagnostics on new files. Fix errors and warnings before proceeding.
Static analysis โ Run sf code-analyzer on the new or changed .cls and .trigger files. Review its output and fix violations before proceeding.
Write tests โ Create test classes following test-guidance.md.
Deploy code and tests Let source tracking which files to deploy
sf project deploy start
Run tests in org
sf apex run test --class-names <TestClassName> --result-format human --wait 10
The task is complete when tests pass in the org.