发现 documentation testing 相关 Skills，比较来源仓库和用途，查看适合你工作流的技能说明。
Write strategic, minimal tests focused on critical user flows and core functionality. Use this skill when deciding which tests to write during feature development. Use this skill when writing unit tests, integr...
Use when implementing ANY new feature or fixing bugs. Test-Driven Development - write tests BEFORE implementation code.
Knowledge and patterns for designing comprehensive test strategies and writing effective tests.
Specialized test resolution that works in parallel to fix specific test failures, enabling faster resolution of test suite issues through isolated fixes without conflicts. Use when multiple test failures need f...
Automates the creation of behavior-driven, fail-first feature tests for user-facing behaviors. Works across any language or framework. Use when features lack behavioral tests, implementing fail-first TDD, ensur...
Executes language-agnostic test suites to validate behavioral correctness, enforce regression safety, and automatically debug or repair test failures. Includes fallback loops, coverage validation, and failure c...
Automates test quality assessment, identifies vanity tests, and guides systematic improvement of test suites. Use when reviewing test suites, identifying shallow tests, enforcing behavioral test standards, or w...
Enforces consistent test quality, structure, and maintainability across any programming language by applying project-wide conventions for test naming, structure, parameterization, and classification. Use for me...
Browser automation, debugging, and performance analysis using Puppeteer CLI scripts. Use for automating browsers, taking screenshots, analyzing performance, monitoring network traffic, web scraping, form automa...
sdd-initで作成したSpecドラフトを入力として、TDDを回せるだけのテスト観点（ハッピー/代表的失敗/境界/不変条件/非機能）をSpecに網羅する。ここではテスト実装・プロダクション実装は行わない。スコープ変更・要件追加もし...
sdd-slice-wishで決めた「推奨スライス」を入力として、仕様書 docs/specs/YYYYMMDD-{name}.md のドラフトを作成する。ここでは実装もテスト実装も行わない。テストケースの網羅（境界・異常・不変条件の列挙）は sdd-test-cas...
TDDのリファクタ(REFACTOR)フェーズを厳密に実行する。全テストGREENを維持したまま、重複排除・命名改善・関心分離など内部構造を改善する。仕様変更が必要なら先にSpecとテスト期待値を更新してから実装を調整する。
TDDのグリーン(GREEN)フェーズを厳密に実行する。REDの「1本だけ」失敗しているテストを通すために、最小限のプロダクションコードだけを実装し、全テストGREENを確認する。余計な機能追加・設計改善はしない。
TDDのレッド(RED)フェーズを厳密に実行する。Spec/受入条件から「1つ」選び、失敗するテストを「1本だけ」追加して実行し、失敗(RED)を確認する。仕様が不明瞭なら実装に進まず、質問/Spec更新提案を行う。
Use when implementing features to write effective tests. Encourages test-first but allows prototyping.
Master Vue Testing - Vitest, Vue Test Utils, Component Testing, E2E with Playwright
Testing Terraform configurations with native tests, Terratest, and validation frameworks
Write production-grade React tests with Testing Library, MSW, and comprehensive coverage patterns
Test Node.js applications with Jest including unit tests, integration tests, mocking, code coverage, and CI/CD integration
JavaScript testing with Jest, Vitest, and Testing Library for comprehensive test coverage.
Backend testing strategies and test automation. Unit, integration, E2E, and load testing with best practices.
Use when about to claim work is complete, fixed, or passing. Run verification commands and confirm output before making any success claims. Evidence before assertions.
Use when implementing any feature or bugfix. Write the test first, watch it fail, write minimal code to pass. Red-Green-Refactor cycle.
Use when encountering any bug, test failure, or unexpected behavior. Always find root cause before attempting fixes. Evidence before assertions.
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库，同一仓库的多个技能可能共享相同数值；它反映仓库关注度，不代表单个技能的安装量或质量评分。