发现 documentation testing 相关 Skills，比较来源仓库和用途，查看适合你工作流的技能说明。
⚡ PRIMARY TOOL for: 'what's tested', 'find test coverage', 'audit test quality', 'missing tests', 'edge cases', 'test patterns'. Uses claudemem v0.3.0 AST with callers analysis for test discovery. GREP/FIND/GL...
Spring Boot 1�� ` �
JavaScript/Node.js testing best practices with Vitest. Use when writing tests, achieving test coverage, or working with JavaScript/TypeScript test files.
Use when creating or editing slash commands - applies TDD to slash command documentation by testing with SlashCommand tool and subagents before deployment, preventing inverted logic and untested conditionals
Use when adding test pseudocode to user stories or implementation guides - creates MEDIUM-IMPLEMENTATION abstraction showing test structure with Vitest terminology, placeholder comments for logic, and strategic...
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure fir...
Use after writing a new skill and/or when testing existing skills, creating skill evaluations, or verifying skills work under pressure - applies TDD/RED-GREEN-REFACTOR to skill documentation by running baseline...
Use when writing Vague (.vague) files - a declarative language for generating realistic test data with superposition, constraints, and cross-references
Use when writing Vague (.vague) files that need realistic test data using faker generators for names, emails, addresses, dates, and more
Use when writing or configuring Vitest tests - assertions, mocking, coverage, and workspace-aware testing for TypeScript projects
Use when writing Vague (.vague) files that need realistic test data using faker generators for names, emails, addresses, dates, and more
Use when writing or modifying Vitest tests to follow best practices for test structure, assertions, mocking, and coverage
Use when writing Vague (.vague) files - a declarative language for generating realistic test data with superposition, constraints, and cross-references
Validates Spec-Driven Development artifacts for completeness, consistency, and quality. Use when checking specs, validating features, reviewing SDD artifacts, or ensuring spec quality before implementation.
Generate pytest unit, integration, and GUI tests for LoRAIro with proper fixtures, mocks, and 75%+ coverage using pytest-qt for PySide6 testing
当开发 OpenHarmony 应用需要使用 JsUnit、UiTest 或 PerfTest 框架进行测试时，或需要模拟 UI 交互、测量性能指标、实现自定义测试运行器时使用
Tester Agent의 심층 QA 프로세스. 커버리지 분석, Edge Case 검증, 심층 테스트, 리포트 생성의 단계를 정의합니다.
Use when implementing any feature or bugfix - requires writing a failing test before writing any production code
Best practices for writing integration tests using Testcontainers and EF Core. Use when creating or modifying integration tests.
End-to-end testing patterns with Playwright. Use when writing or debugging E2E tests, focusing on reliability, isolation, and flakiness prevention.
Unit testing patterns for .NET applications using EF Core In-Memory Provider, AAA structure, test data helpers, and TDD workflows. Use when writing unit tests for Application Services, domain logic, or data acc...
Integration testing performance optimization, test parallelization, cleanup strategies, and CI/CD categorization patterns. Use when optimizing test execution speed, managing test data, or structuring tests for...
Writes and reviews user stories with acceptance criteria following standard categories. Use when creating user stories, defining acceptance criteria, or reviewing story completeness for GloboTicket features.
Defines test scenarios using Given-When-Then format and maps tests to acceptance criteria. Use when writing technical specifications, defining unit and integration test requirements, or ensuring test coverage f...
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库，同一仓库的多个技能可能共享相同数值；它反映仓库关注度，不代表单个技能的安装量或质量评分。