test-review
Use when reviewing test design or test changes without implementing them.
- License 许可
- GPL-3.0
- 最近更新
- 2026-11-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- test-review
- description
- Use when reviewing test design or test changes without implementing them.
03 SKILL.md 正文
Read the testing contract. For each test, identify the behavior question, system under test, inputs, oracle, layer, deterministic setup, and meaningful failure signal. Check representative, empty, boundary, invalid, and historical bug cases; tautologies, accidental passes, over-mocking, order dependence, flakiness, and green-suite or coverage overclaims.
Return severity-ranked findings with exact file/line evidence, a minimal fix,
commands not run, and remaining risk. Do not rewrite or run tests unless the
request explicitly changes review scope. Use is-good-test when its dedicated
experiment-design predicate matches.
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