القائمة
Design a testing strategy and pyramid for a repository or change. Use when planning unit, component, contract, integration, e2e, smoke, fuzz, or benchmark coverage.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | testing-pyramid |
| description | Design a testing strategy and pyramid for a repository or change. Use when planning unit, component, contract, integration, e2e, smoke, fuzz, or benchmark coverage. |
Map current tests to pyramid levels. Identify gaps and flaky risks. Recommend additions with priority. Do not invent passing test counts.
Primary prompts:
prompts/16_testing_pyramid_and_unit_tests.mdprompts/119_test_seam_refactor.mdprompts/98_prompt_regression_suite.mdCrafting Kit architectural decision records covering risk gates, execution as a first class stage, no assumption execution, and tool permission enforcement. Use when you need the rationale behind a contract or boundary.
Audit API, CLI, OpenAPI, GraphQL, and CLI help against documented contracts and example outputs. Use when validating contract drift or releasing public surfaces.
Audit API contract compatibility, deprecation strategy, and version migration. Use when planning a contract change.
Answer specific repository questions with cited paths and excerpts. Use when the user asks where something is, how it works, or what depends on it.
Compare the project to competitors using source evidence and allowed research. Use when preparing positioning, market readiness, or product narrative.
Assess database migration reversibility, idempotency, transactional safety, and destructive-change risk. Use before applying or shipping a migration.