菜单
Analyze testing approach — what to test, how to test, coverage gaps, and test quality. Trigger on /test-strategy, or when planning tests, reviewing test gaps, or debugging flaky tests.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Control shell, filesystem, MCP, browser, external APIs, and risky tools. Enforce read-only-before-write, least-privilege, and verification discipline. Trigger on /agent-tool-safety, or when using shell commands, file operations, MCP tools, browser automation, or external APIs.
Final sanity check on AI-generated code before merging. Run the checklist to catch common failure modes. Trigger on /ai-coding-agent-review, or before finalizing any significant AI-generated change.
Review API design — endpoints, types, contracts, error handling, versioning, and consistency. Trigger on /api-design, or when designing or reviewing API specifications.
Implement backend API endpoints — routing, middleware, input validation, error handling, authentication, rate limiting, file upload. Trigger on /api-implementation, or when building endpoints, adding middleware, handling file uploads, or implementing API security.
Record architecture decisions as ADRs — compare options, document trade-offs, and track rationale. Trigger on /architecture-decision, or when choosing libraries, designing modules, splitting systems, or making significant technical decisions.
Make the agent continue work without asking unnecessary questions. Enforce the ask-less policy from CLAUDE.md. Trigger on /ask-less-execution, or when the agent is asking too many clarifying questions instead of discovering answers.
基于 SOC 职业分类
| name | test-strategy |
| description | Analyze testing approach — what to test, how to test, coverage gaps, and test quality. Trigger on /test-strategy, or when planning tests, reviewing test gaps, or debugging flaky tests. |
| user-invocable | true |
| allowed-tools | Read, Grep, Glob, Bash |
Decide what to test and how. Focus on risk, not coverage percentages.
| Type | When to use | When NOT to use |
|---|---|---|
| Unit | Pure logic, utilities, isolated components | When test needs DB/network/filesystem |
| Integration | DB queries, API routes, external service calls | When setup cost > value of test |
| E2E | Critical user journeys, payment flows | For internal implementation details |
| Snapshot | UI output, serialization formats | For large data that changes often |
This skill learns from experience. Mechanism:
.claude/experience/test-strategy.md at skill start to benefit from past lessons..claude/experience/test-strategy.md after use if you learned something new.YYYY-MM-DD: <lesson> — one line per entry.