salesforce-test
Use when generating Apex tests, designing test data factories, sanitising sandbox data, or improving Apex test coverage / quality.
What this skill does
# Salesforce test skill
## Coverage targets
- Hard floor: 75% (deploy gate)
- Soft floor: 85% (PR gate)
- Per-class: 75% minimum for any class touched in the PR
Coverage is a floor, not a ceiling. **Behaviour coverage** > line coverage.
## Test data factories
Pattern:
```apex
@IsTest
public class TestDataFactory {
public static List<Account> createAccounts(Integer n) {
List<Account> accs = new List<Account>();
for (Integer i = 0; i < n; i++) {
accs.add(new Account(Name = 'Test ' + i));
}
insert accs;
return accs;
}
}
```
Rules:
- One factory per object
- `@IsTest` on the class so it doesn't count against org space
- Always insert and return
- Take an `Integer n` param — bulkify by default
## Bulk patterns
Tests must verify behaviour at 200+ records (the trigger batch boundary):
```apex
@IsTest static void shouldBulkInsert() {
List<Account> accs = TestDataFactory.createAccounts(200);
Test.startTest();
AccountService.process(accs);
Test.stopTest();
System.assertEquals(200, [SELECT COUNT() FROM Account WHERE IsProcessed__c = true]);
}
```
## Sanitising sandbox data
For full-copy sandboxes refreshed from prod:
```apex
// Data masking via Apex script
List<Contact> cs = [SELECT Id FROM Contact LIMIT 50000];
for (Contact c : cs) {
c.Email = 'masked+' + c.Id + '@example.invalid';
c.Phone = null;
c.MailingStreet = '[redacted]';
}
update cs;
```
For larger volumes: use Bulk API 2.0 from a script, or Salesforce Data Mask (paid).
## Common Apex test bugs
- **Test sees prod data** — `@IsTest(SeeAllData=true)` left on, remove unless absolutely needed
- **`MIXED_DML_OPERATION`** — setup objects (User, Profile) require `System.runAs(...)` block
- **Test passes locally, fails in CI** — depends on running user (System vs default), org settings, or record types not in test data
- **Coverage shows 100% but logic isn't tested** — assertions missing; line covered ≠ behaviour verified
## When to mock
- HTTP callouts: `Test.setMock(HttpCalloutMock.class, new MyMock())`
- Async chain endpoints: stub the next step
- External objects: mock the layer above
Don't mock domain logic — test it directly.
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.