test-generator
Test Generator
Generate well-structured, maintainable test suites that provide confidence in code correctness. Follow the test pyramid approach: many unit tests, fewer integration tests, minimal E2E tests.
Test Generation Workflow
Step 1: Analyze the Code Under Test
- Read the source file(s) to understand functionality.
- Identify all public functions, methods, and exported interfaces.
- Map code paths — branches, loops, error handlers, early returns.
- Identify external dependencies — APIs, databases, file system, third-party services.
- Note any existing tests to avoid duplication and maintain consistency.
Step 2: Identify Test Cases
For each function or method, identify:
Happy Path Cases
More from kaakati/sdh-claude-skills
refactor
Safely refactor code using Fowler's patterns with test-first methodology and incremental steps. Use this skill whenever someone asks to refactor code, reduce technical debt, extract patterns, restructure modules, or says things like "refactor this", "clean up this code", "extract this into a service", "this code smells", "reduce duplication", "decompose this function", or "restructure this module". Also trigger for code smell identification, large-scale codebase transformations, or safe migration of legacy code.
2ui-ux-patterns
|
2architecture-advisor
Evaluate architectural decisions, design system components, produce ADRs, and assess technical debt. Use this skill whenever someone asks to design a system, evaluate architecture, create an ADR, plan a large refactor, choose between technologies, or says things like "how should we architect X", "write an ADR", "evaluate this design", "what are the tradeoffs", "review the architecture", or "should we use X or Y". Also trigger for bounded context design, scalability planning, or migration strategy.
2web-design-guidelines
|
2react-best-practices
|
2clean-architecture
Validate and implement Clean Architecture patterns including entity/use-case/adapter/framework layer separation, dependency direction enforcement, and architectural conformance checking. Use this skill whenever someone asks about architecture validation, layer boundaries, dependency direction, or says things like "check architecture", "validate clean architecture", "are my layers correct", "dependency direction", "refactor to clean architecture", "layer violation", or "architectural conformance". Also trigger for discussions about service object patterns, controller responsibilities, or domain model isolation.
2