test-plan-generator
Automatically generate comprehensive QA test plans when user mentions testing requirements, QA needs, or asks what should be tested. Analyzes code changes and features to create structured test scenarios. Invok...
Discover blockchain testing skills, compare source repositories and read the instructions for each workflow.
Automatically generate comprehensive QA test plans when user mentions testing requirements, QA needs, or asks what should be tested. Analyzes code changes and features to create structured test scenarios. Invok...
Automatically generate test scaffolding when user writes new code without tests or mentions needing tests. Supports unit, integration, e2e, and data tests for PHP and JavaScript. Invoke when user mentions "test...
End-to-end verification for the site-visit (Step 7) flow. Use when you need to reproduce or validate that the system reaches the site-visit prompt/options and can proceed to confirmation, either via determinist...
End-to-end verification for the site-visit (Step 7) flow. Use when you need to reproduce or validate that the system reaches the site-visit prompt/options and can proceed to confirmation, either via determinist...
Maintain and extend prompt-injection defenses. Use when adding new user-input surfaces, changing prompt templates, or when a new injection pattern is observed; run the security regression suite and add a minima...
Setup and verification for MCP tooling used in OpenEvent-AI (filesystem, Context7 docs, LSP/Pyright, Playwright). Use when onboarding a new developer/agent or when Codex/Claude cannot access LSP, browser automa...
Intent-based specification tests evaluated by LLM-as-judge. Use when the user asks to "create spec tests", "write intent tests", "TDD with intent", "natural language tests", or wants tests that capture WHY, not...
General-purpose testing for all test types - unit, integration, E2E, component tests
Generate and execute test plans based on documentation. Use after implementation to verify changes work correctly. Integrates with browser testing for UI verification.
This skill should be used when user asks "/playwright-test", "/test", "test automation", "Playwright test", "E2E test", "web test", "multi-agent test", "functional/visual/API/performance test", "테스트 자동화",...
テストコードを書く・修正する前に必ず参照する。テスト作成・修正・レビュー・リファクタリング時に使用。
**TDD GUARDIAN**: '테스트 작성', '테스트 만들어', 'TDD', '단위 테스트', '통합 테스트', '커버리지', 'mock', '모킹' 요청 시 자동 발동. *.test.ts/*.spec.ts/test_*.py 파일 작업 시 자동 적용. Fake Test 탐지, 80% 커...
Measure test coverage and identify untested areas. Use for coverage checks.
Generate unittest test files for untested cvp/ modules. Use for test creation.
Generates comprehensive unit tests for the selected code. It follows the project's testing conventions, ensures high coverage, and handles edge cases.
Generates comprehensive BDD/Gherkin tests for features. Triggers when user needs to write tests, create test scenarios, add test coverage, or verify feature completeness.
Generates a rigorous, engineering-ready specification for a UI component. Focuses on strict API contracts (TypeScript), deterministic state logic (Mermaid), and verifiability (Gherkin). Use when designing new U...
Jest testing guidelines, mocking strategies, and test structure patterns for unit tests.
Orchestrates test execution for the Nomos monorepo following TESTING_GUIDE.md standards. Use this when running tests, debugging test failures, validating coverage, or executing verification checklists from AGEN...
Review existing tests for completeness, quality issues, and common mistakes
テストコードを作成する際に使用します。ユニットテスト、統合テスト、エンドツーエンドテストなど、あらゆる種類のテストコードを生成するためにこのスキルを利用してください。
ブラウザでの動作確認・テストガイド
Use when writing unit tests, integration tests, or end-to-end tests in Python. Also use for implementing test fixtures, mocking, parametrization, async testing, or coverage analysis. NOT when using other testin...
実装完了後のマルチ視点ストレステストフロー。複数の検証エージェントが並列で品質を検証し、コード生成なしで問題を検出
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.