test-assess
Use when assessing a test strategy, suite quality, risk coverage, flakiness, or whether existing tests provide meaningful confidence.
- License 许可
- GPL-3.0
- 最近更新
- 2026-11-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- test-assess
- description
- Use when assessing a test strategy, suite quality, risk coverage, flakiness, or whether existing tests provide meaningful confidence.
03 SKILL.md 正文
Read ../using-testpowers/references/testing-contract.md. Identify the
behavior and risks, test layers present, missing representative/empty/boundary/
invalid cases, historical bugs, entrypoint coverage, runner commands, speed,
isolation, and environment assumptions.
Do not edit. Reject tautological assertions, green-suite overclaims, tests that
only exercise mocks, and coverage percentages presented as correctness. Rank
findings by user risk and name the smallest suitable leaf (test-unit,
test-integration, test-regression, test-property, test-snapshot,
test-smoke, test-entrypoint, or test-coverage).
Return exact evidence paths, commands tried, unavailable tooling, and a prioritized test plan.
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