testing
0
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.
TravisBumgarner
testing-security
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
testing
0
docs-test-review
ドキュメント・テスト品質レビュー - コメント品質、API仕様、テストの意味、カバレッジを統合評価
DaichiHoshina
testing-security
testing
0
implementing-tests
You are an expert implementer of unit and integration tests.
tmitchel2
testing-security
testing
0
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.
jaredlander
testing-security
testing
0
migestion-test-web
Web E2E testing patterns for MiGestion - Playwright, page objects. Trigger: When writing or running E2E tests.
eduardbar
testing-security
testing
0
generate-test-suite
Standard procedure for generating comprehensive pytest test suites following airline-discount-ml project patterns and test instructions.
ei-stanko-zdravkovic
testing-security
testing
0
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.
foolishimp
testing-security
testing
0
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.
ahupp
testing-security
testing
0
server-test-guard
백엔드 코드(Controller, Service, DTO, Entity, Repository) 및 통합 테스트 코드(tests/integration) 변경 시 반드시 사용. 테스트 코드 점검, 수정, 검증까지 완료해야 작업이 끝난 것으로 간주. app/backend/ 또는 tests/integration/ 하위 파일 수정 후 이 skill을 자동 적용.
SolidCitadel
testing-security
testing
0
test-generator
Generate unittest test files for untested cvp/ modules. Use for test creation.
cvprun
testing-security
testing
0
test-driven
Implement test-driven development (TDD) practices. Write tests first, then implementation.
guvnr-dev
testing-security
testing
0
playwright
Complete guide to using Playwright MCP server with Claude Code
Lordsisodia
testing-security
testing
0
firebase-testing
Guide for testing Firebase Admin SDK with Vitest mocks. Use when writing tests that involve Firebase Auth, Firestore, or Firebase App.
janisto
testing-security
testing
0
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.
dpietersz
testing-security
testing
0
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.
I2olanD
testing-security
testingmarketplace
0
cui-javascript-unit-testing
Jest unit testing standards covering configuration, test structure, testing patterns, and coverage requirements
cuioss
testing-security
testing
0
using-browser-mode
Set up Vitest browser mode with Playwright or WebDriverIO providers, use page and userEvent APIs, test components. Use when testing browser-specific code or UI components.
djankies
testing-security
testing
0
ticket-status
Programmatic verification of KB state: tickets, phases, tests, integrity. Provides scripts for automated checking at each workflow stage. SCRIPTS: - check_ticket.py: Ticket docs, tests, final status → next step - check_phase.py: Phase progress, all tickets complete? - check_tests.py: Trajectory, RED verification, coverage vs spec - check_integrity.py: Index.md matches dirs, roadmap has all active items Use when: - Checking ticket/phase completion - Validating before commit/archive - CI/CD automation - User says "status", "check", "verify"
jayprimer
testing-security