test-integration
Use when testing a meaningful seam between modules, packages, filesystems, databases, services, compilers, or external tools.
- License 许可
- GPL-3.0
- 最近更新
- 2026-11-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- test-integration
- description
- Use when testing a meaningful seam between modules, packages, filesystems, databases, services, compilers, or external tools.
03 SKILL.md 正文
Read the testing contract. Name the seam and the failure that a unit test cannot detect. Use the smallest real components and controlled fixture; avoid mocking the very boundary whose compatibility matters. Cover successful data flow, malformed/empty input, timeout or unavailable dependency where relevant, and cleanup/repeatability.
Record setup, teardown, environment, runner command, expected signal, cost, and
whether the test is opt-in or required. Keep credentials and private data out
of fixtures. If the test is only install/user-path confidence, hand off to
test-entrypoint or test-smoke.
04 同仓库更多 Skills
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code