一键导入
analyzing-test-effectiveness
Use to audit test quality with SRE scrutiny - identifies weak tests, missing cases, and creates task docs for improvements
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use to audit test quality with SRE scrutiny - identifies weak tests, missing cases, and creates task docs for improvements
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when shaping a feature before implementation - turns rough ideas into an approved markdown spec and local task directory
Use to execute an approved local markdown task directory iteratively - work the current Now slice, update docs, then stop
Use when implementation is complete and verified - delete finished local task docs, present integration options, and clean up safely
Use for advanced markdown task-doc operations - split work, reprioritize slices, delete finished local task dirs, and keep docs clean
Use after executing a task directory - verifies implementation against plan.md, acceptance checks, and anti-goals
Use when starting any conversation - establishes skill selection and the local task-doc workflow
| name | analyzing-test-effectiveness |
| description | Use to audit test quality with SRE scrutiny - identifies weak tests, missing cases, and creates task docs for improvements |
<skill_overview> High coverage is not the goal. Tests must catch real failures and justify their maintenance cost. </skill_overview>
<rigidity_level> MEDIUM FREEDOM - Follow the audit flow strictly, but adapt the exact categories and examples to the codebase. </rigidity_level>
<quick_reference>
<when_to_use>
<the_process>
Look for:
For every weak area, say what real bug it would or would not catch.
Create or update a task directory that captures:
Use sre-task-refinement to harden the improvement plan before implementation.
</the_process>