name	test-generate
description	Generates unit tests for a file or function with full coverage of edge cases
argument-hint	<file-path> [function-name]
user-invocable	true
allowed-tools	Read Glob Grep Edit
effort	medium

Target: $1 $2

Read the file and understand:
- What framework is used (Jest, Vitest, Mocha, pytest, Go test, etc.) - check existing test files for patterns
- The function/class signatures, types, return values
- Existing tests (if any) to match style
Identify test cases:
- Happy path (normal usage)
- Edge cases (null, undefined, empty, boundary values)
- Error cases (thrown exceptions, rejected promises)
- Async behavior if applicable
Write tests following the project's existing test style.
Place the test file next to the source or in __tests__/ - match project convention.
Show a summary: N tests covering X scenarios.

Más de este repositorio

mismo repositorio

Analyzes the current session's token usage, pinpoints where tokens were wasted, and produces concrete optimization actions

Generates API documentation from route definitions (Express, Fastify, Hono, etc.)

Adds caching to expensive operations - Redis, in-memory, HTTP cache headers

Staged değişiklikleri analiz edip Conventional Commits formatında commit mesajı oluşturur

Reports cyclomatic complexity hotspots and refactoring suggestions

Finds unused functions, variables, exports, and dependencies across the codebase

name	test-generate
description	Generates unit tests for a file or function with full coverage of edge cases
argument-hint	<file-path> [function-name]
user-invocable	true
allowed-tools	Read Glob Grep Edit
effort	medium

Target: $1 $2

Read the file and understand:
- What framework is used (Jest, Vitest, Mocha, pytest, Go test, etc.) - check existing test files for patterns
- The function/class signatures, types, return values
- Existing tests (if any) to match style
Identify test cases:
- Happy path (normal usage)
- Edge cases (null, undefined, empty, boundary values)
- Error cases (thrown exceptions, rejected promises)
- Async behavior if applicable
Write tests following the project's existing test style.
Place the test file next to the source or in __tests__/ - match project convention.
Show a summary: N tests covering X scenarios.