test-coverage
Use when measuring, interpreting, or improving test coverage and identifying meaningful untested behavior.
- License 许可
- GPL-3.0
- 最近更新
- 2026-11-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- test-coverage
- description
- Use when measuring, interpreting, or improving test coverage and identifying meaningful untested behavior.
03 SKILL.md 正文
Read the testing contract. Run the repository's coverage command and inspect uncovered branches, error paths, boundaries, public entrypoints, and historical bugs. Treat the percentage as a navigation signal, not a quality verdict.
Prioritize gaps by user risk and add the smallest meaningful test at the right layer. Check that coverage excludes generated/vendor code intentionally and that the command is reproducible. Report baseline, changed result, command, scope, and remaining blind spots; never inflate coverage with tautological assertions.
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