菜单
Writes tests that match your project's existing test patterns and conventions. Detects the test framework in use, reads nearby test files to understand naming and structure conventions, and generates tests for the code you point it at — without introducing a different style.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Guides you through designing and writing a new Claude skill from scratch — determines the right complexity tier, writes the SKILL.md with correct frontmatter and instructions, and scaffolds any supporting assets, references, or scripts the skill needs.
Guides you through designing and packaging a complete skillset — determines what skills belong together, writes the SKILLSET.md manifest, identifies shared assets, and produces the full directory layout with all skill files ready to install.
Generates structured competitor breakdowns from information you provide. Uses a bundled analysis framework to evaluate competitors across consistent dimensions — positioning, pricing, features, weaknesses, and moat — and outputs a formatted report ready to share with stakeholders or paste into a product document.
Produces structured summaries of academic or technical papers. Fills a consistent template covering abstract, key contributions, method, results, limitations, and relevance. Calibrates terminology and depth to a named audience using the shared audience personas reference — so the summary is useful to the right reader, not just accurate.
Explains complex technical topics in plain language calibrated to a named audience. Loads a shared audience personas reference to determine vocabulary level, assumed prior knowledge, and preferred explanation style — so the explanation lands for that specific reader, not for a generic one.
Produces CHANGELOG entries from git history following the Keep a Changelog format. Uses a bundled script to extract commits since the last tag, classifies them into changelog sections using the shared commit conventions reference, and outputs a ready-to-paste release block.
| name | test-writer |
| description | Writes tests that match your project's existing test patterns and conventions. Detects the test framework in use, reads nearby test files to understand naming and structure conventions, and generates tests for the code you point it at — without introducing a different style. |
| version | 1.0.0 |
| tags | ["testing","developer","jest","vitest","pytest","workflow"] |
| author | skilldex-examples |
Use this skill when the user wants to write tests for a specific function, module, or feature.
scripts/detect-framework.sh — detects the test framework used in a project from package.json, config files, and file extensions. Ask the user to run it if the framework is not obvious from context.references/testing-patterns.md — describes common structural conventions for each supported framework (describe/it nesting, setup/teardown, assertion style, mocking approach). Load this before writing any tests.Identify the target: Ask the user which function, class, or module they want tested, and get the source code if not already in context.
Detect the framework: If not already clear, ask the user to run:
bash path/to/test-writer/scripts/detect-framework.sh
Use the output to determine the framework. If detection fails, ask directly.
Read existing tests: Ask the user to share one or two existing test files from the project. This is critical — use them to infer:
*.test.ts, *.spec.js, _test.go, etc.)Load testing patterns: Consult references/testing-patterns.md for the detected framework's standard conventions. Reconcile with what you observed in existing test files — project conventions override the reference when they conflict.
Write the tests: Generate a test file that:
Output: Present the full test file in a code block with the correct file extension.
test() calls, don't introduce describe blocks