一键在 Manus 中运行任何 Skill

开始使用

test-gen

星标7

分支8

更新时间2026年5月2日 13:41

Use when generating tests for untested code — happy path, edge cases, error handling

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

KeiSeiLab

KeiSeiLab/KeiSeiKit

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

When to use

Generating unit tests for a specific function or file (happy path, edge cases, error handling).
Writing tests first (TDD) before implementing new functionality.
Use /test-gen for per-function unit tests; use /test-matrix for project-wide testing strategy.

Complements /test-matrix. /test-gen owns per-function unit tests (happy / edge / error). /test-matrix owns project-wide testing strategy (fuzz / property / load / e2e / mutation) and CI wiring. Use /test-gen for a specific function, /test-matrix at project kickoff or when coverage gaps span paradigms. See skills/test-matrix/SKILL.md.

Test Generation Workflow

Step 1: Analyze Target

Read the target file/function completely
Identify: inputs, outputs, side effects, dependencies, error paths
Check existing test files — don't duplicate

Step 2: Detect Framework

Auto-detect test framework from project:
- Python: pytest (conftest.py, pytest.ini) or unittest
- JS/TS: jest (jest.config), vitest (vitest.config), mocha
- Flutter: flutter_test
- Go: built-in testing
Match existing test file naming: test_*.py, *.test.ts, *_test.dart, *_test.go

Step 3: Plan Test Cases

Categories (in order of priority):

Happy path — normal expected usage (2-3 cases)
Edge cases — boundaries, empty inputs, max values (2-3 cases)
Error handling — invalid inputs, missing data, network errors (1-2 cases)
Integration — only if function interacts with external services (1 case with mock)

Step 4: Write Tests

Follow existing test patterns in the project
Use descriptive test names: test_<function>_<scenario>_<expected>
One assertion per test (prefer)
Mock external dependencies, not internal logic
Use fixtures/factories from existing test infrastructure

Step 5: Run & Verify

Run new tests — all must pass
Run full test suite — no regressions
Check coverage delta if coverage tool available

Step 6: Commit

test: add tests for <target>

同仓库更多 Skills

同仓库

research

KeiSeiLab/KeiSeiKit

Deep research on any topic using parallel agents, web search, and cross-referencing. Use when user asks to research, investigate, or deeply analyze a topic, technology, library, or concept. Triggers on keywords like "research", "investigate", "deep dive", "find out everything about". Supports `--angle` presets for common specializations (competitors, design-refs).

2026-06-017

animate

KeiSeiLab/KeiSeiKit

Gateway router for web animation work. Picks between /scroll-animation, /motion-design, or /ai-animation via one AskUserQuestion call, then hands off. Does NOT implement animation — the downstream skills remain the source of truth for their respective domains.

2026-05-307

batch-workflow

KeiSeiLab/KeiSeiKit

Use when running multi-skill pipelines — new-feature, marketing-launch, design-to-code, web-creation, full-audit, rag-setup workflows

2026-05-307

compose-solution

KeiSeiLab/KeiSeiKit

Meta-orchestrator — converts a free-text task description into the right artefact(s) (agent, skill, hook, rule, or block) by composing existing KeiSeiKit primitives. Pure-click decision chain except the single intake field. Enriches `_blocks/` over time via Phase 6 block-augmentation — the kit gets smarter with every invocation.

2026-05-307

design-inspiration

KeiSeiLab/KeiSeiKit

Deprecated alias for /research with the design-refs angle preset. Routes to /research focused on design patterns, visual archetype references, and award-winning site teardowns.

2026-05-307

dev-guard

KeiSeiLab/KeiSeiKit

Continuous parallel quality gate during development — 3 backend agents (security/perf/structure) check every significant code change in real-time. Run after writing code, before committing.

2026-05-307

Test Generation Workflow

Step 1: Analyze Target

Read the target file/function completely

Identify: inputs, outputs, side effects, dependencies, error paths

Check existing test files — don't duplicate

Step 2: Detect Framework

Auto-detect test framework from project:

Python: pytest (conftest.py, pytest.ini) or unittest
JS/TS: jest (jest.config), vitest (vitest.config), mocha
Flutter: flutter_test
Go: built-in testing

Match existing test file naming: test_*.py, *.test.ts, *_test.dart, *_test.go

Step 3: Plan Test Cases

Categories (in order of priority):

Happy path — normal expected usage (2-3 cases)

Edge cases — boundaries, empty inputs, max values (2-3 cases)

Error handling — invalid inputs, missing data, network errors (1-2 cases)

Integration — only if function interacts with external services (1 case with mock)

Step 4: Write Tests

Follow existing test patterns in the project

Use descriptive test names: test_<function>_<scenario>_<expected>

One assertion per test (prefer)

Mock external dependencies, not internal logic

Use fixtures/factories from existing test infrastructure

Step 5: Run & Verify

Run new tests — all must pass

Run full test suite — no regressions

Check coverage delta if coverage tool available

Step 6: Commit

test: add tests for <target>

name	test-gen
description	Use when generating tests for untested code — happy path, edge cases, error handling
arguments	[{"name":"target","description":"File path or function name to test","required":true}]