defense-in-depth-validation
Validate at every layer data passes through to make bugs impossible
e2e-playwright-diagnosis
Diagnose and resolve E2E test failures in Playwright. This skill should be used when E2E tests fail and need investigation, when Playwright test errors require root cause analysis, or when test failures need to be reproduced in the browser for debugging. Orchestrates MCP tools (Playwright, Chrome DevTools, Serena) and delegates code fixes to specialized agents.
ralph-test
Use this skill when writing tests, especially when working in TDD style to define tests before the actual functions are complete. This is the "Red" phase of TDD.
docs-test-review
ドキュメント・テスト品質レビュー - コメント品質、API仕様、テストの意味、カバレッジを統合評価
implementing-tests
You are an expert implementer of unit and integration tests.
unit-testing
Write comprehensive unit tests for code. Use when asked to (1) write tests for new or existing code, (2) add unit tests, (3) test a function/module/class, (4) verify code still works after changes, (5) create test coverage, or when phrases like "write tests", "add tests", "test this", "make sure this works" appear. Supports Python, JavaScript, R, Rust, Go, C++, SQL, Bash, Ansible, Kubernetes/Kustomize, Docker, and Docker Compose.
migestion-test-web
Web E2E testing patterns for MiGestion - Playwright, page objects. Trigger: When writing or running E2E tests.
generate-test-suite
Standard procedure for generating comprehensive pytest test suites following airline-discount-ml project patterns and test instructions.
implement-step-definitions
Implement step definitions for Gherkin scenarios, translating Given/When/Then into executable test code. Use after write-scenario when scenarios are defined but step definitions are missing.
summarize-cpython-failures
Summarize CPython test failures from cpython_full_test_run.log (and cpython_full_test_run_summary.txt if present), compute passed/total counts for test files and test cases, and group failures by likely root cause. Use when asked to summarize or categorize failures from a CPython regrtest run in this repo.
server-test-guard
백엔드 코드(Controller, Service, DTO, Entity, Repository) 및 통합 테스트 코드(tests/integration) 변경 시 반드시 사용. 테스트 코드 점검, 수정, 검증까지 완료해야 작업이 끝난 것으로 간주. app/backend/ 또는 tests/integration/ 하위 파일 수정 후 이 skill을 자동 적용.
test-generator
Generate unittest test files for untested cvp/ modules. Use for test creation.
test-driven
Implement test-driven development (TDD) practices. Write tests first, then implementation.
playwright
Complete guide to using Playwright MCP server with Claude Code
firebase-testing
Guide for testing Firebase Admin SDK with Vitest mocks. Use when writing tests that involve Firebase Auth, Firestore, or Firebase App.
testing-test-writing
Write minimal, focused tests that cover core user flows and primary workflows without over-testing during development. Use this skill when deciding what to test, writing behavior-focused tests, naming test cases clearly, mocking external dependencies, or keeping tests fast. Apply when completing feature implementation and adding strategic tests, testing critical paths rather than edge cases, or deferring edge case testing to dedicated testing phases.
test-design
Apply test pyramid principles, coverage targets, and framework-specific patterns. Use when designing test suites, reviewing test coverage, or implementing tests. Covers Jest, Pytest, and common testing frameworks with naming conventions and organization patterns.
