test-writer
Writes comprehensive test cases including unit tests, integration tests, and E2E tests. Use when implementing test requirements from tasks. Creates tests that cover happy paths, edge cases, error conditions, and follow testing best practices.
What this skill does
# Test Writer Skill
## Instructions
1. Analyze test requirements from task
2. Identify what needs to be tested (functions, components, endpoints)
3. Write unit tests for individual functions/components
4. Write integration tests for component interactions
5. Write E2E tests for user flows (if applicable)
6. Cover happy paths, edge cases, and error conditions
7. Ensure tests are independent and isolated
8. Return test implementation with:
- Test files
- Test cases covering all scenarios
- Setup and teardown
- Mocking where needed
- Assertions and expectations
## Examples
**Input:** "Write tests for calculateTotal function"
**Output:**
```javascript
// tests/utils.test.js
describe('calculateTotal', () => {
test('calculates total for valid items array', () => {
const items = [
{ price: 10.00 },
{ price: 20.00 },
{ price: 5.00 }
];
expect(calculateTotal(items)).toBe(35.00);
});
test('returns 0 for empty array', () => {
expect(calculateTotal([])).toBe(0);
});
test('returns 0 for null input', () => {
expect(calculateTotal(null)).toBe(0);
});
test('returns 0 for undefined input', () => {
expect(calculateTotal(undefined)).toBe(0);
});
test('handles items with zero price', () => {
const items = [
{ price: 10.00 },
{ price: 0 },
{ price: 5.00 }
];
expect(calculateTotal(items)).toBe(15.00);
});
});
```
## Test Types
- **Unit Tests**: Test individual functions/components in isolation
- **Integration Tests**: Test component interactions, API integrations
- **E2E Tests**: Test complete user flows
- **Snapshot Tests**: Test component rendering (if applicable)
- **Performance Tests**: Test performance characteristics (if needed)
## Test Coverage Areas
- **Happy Paths**: Normal, expected behavior
- **Edge Cases**: Boundary conditions, empty inputs, null values
- **Error Conditions**: Invalid inputs, error handling
- **State Changes**: Component state transitions
- **User Interactions**: Click, input, navigation
- **API Responses**: Success and error responses
## Best Practices
- **Independent Tests**: Each test should be independent
- **Clear Names**: Descriptive test names
- **Arrange-Act-Assert**: Follow AAA pattern
- **Mock External Dependencies**: Mock APIs, databases, etc.
- **Test One Thing**: Each test should test one behavior
- **Fast Tests**: Tests should run quickly
- **Maintainable**: Tests should be easy to understand and maintain
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.