Agent Skills › franklioxygen/agent-workflows › test-strategy

test-strategy

GitHub

设计高价值测试策略，通过映射行为与覆盖率、识别边缘案例及选择验证命令，避免脆弱或低信号测试。适用于生成测试计划、覆盖矩阵、回归策略及QA清单等场景。

skills/test-strategy/SKILL.md franklioxygen/agent-workflows

Trigger Scenarios

用户请求测试计划用户请求覆盖矩阵用户请求回归策略用户请求QA检查清单用户请求验证方法

Install

npx skills add franklioxygen/agent-workflows --skill test-strategy -g -y

More Options

Use without installing

npx skills use franklioxygen/agent-workflows@test-strategy

指定 Agent (Claude Code)

npx skills add franklioxygen/agent-workflows --skill test-strategy -a claude-code -g -y

安装 repo 全部 skill

npx skills add franklioxygen/agent-workflows --all -g -y

预览 repo 内 skill

npx skills add franklioxygen/agent-workflows --list

SKILL.md

Frontmatter

{
    "name": "test-strategy",
    "description": "Design high-value test strategies for features, bug fixes, refactors, migrations, and reviews by mapping behavior to coverage, identifying missing edge cases, selecting validation commands, and avoiding brittle or low-signal tests. Use when Codex is asked for a test plan, coverage matrix, regression strategy, QA checklist, or validation approach."
}

Test Strategy

Quick Start

Run scripts/test_inventory.py <path> when a repository path is available.
Read references/test-strategy-checklist.md before finalizing the test plan.
Follow shared safety, validation, and scope rules in ../_shared/references/skill-operating-rules.md.
Map tests to observable behavior, not implementation details.
Prefer targeted validation first, then broader validation when risk justifies it.
Do not edit code unless the user explicitly asks for implementation.

Strategy Workflow

Identify changed or proposed behavior.
List risk areas: permissions, data shape, API contracts, UI states, errors, concurrency, migrations, performance, and integrations.
Inventory existing test structure and commands:

python3 scripts/test_inventory.py /path/to/repo

Produce a coverage matrix:

| Behavior | Existing coverage | Needed test | Priority |
| --- | --- | --- | --- |
| <behavior> | covered / partial / missing | <test idea> | P0 / P1 / P2 |

Separate automated tests from manual QA and validation commands.
Call out tests that should not be updated because they assert stable behavior.

Output Rules

Include exact scenarios, inputs, expected results, and why each test matters.
Mark regression tests that should fail before the fix and pass after it.
State skipped tests or validations with reasons.
Flag weak tests: broad snapshots, tautological assertions, timing-sensitive tests, and tests that mirror implementation instead of behavior.