test-coverage-requirements
Enforces test coverage requirements: models (100%), repositories (95%), BLoCs (100%), use cases (100%), services (90%). Use when writing tests, reviewing test coverage, or ensuring adequate test coverage.
Découvrez les skills documentation testing, comparez leurs dépôts et consultez leurs instructions.
Enforces test coverage requirements: models (100%), repositories (95%), BLoCs (100%), use cases (100%), services (90%). Use when writing tests, reviewing test coverage, or ensuring adequate test coverage.
Run targeted Playwright checks for Lithuanian HTML practice tests in /mnt/c/Programming/Projects/Pets/eduardmikhailau.github.io. Use when the user says “run tests” or after adding/editing HTML files under tests...
Generates test templates: unit, widget, integration, service tests following project patterns. Use when creating new tests or ensuring tests follow project standards.
Fix ServiceResult pattern mistakes causing test failures and type errors. Use when seeing "dict object has no attribute success", "mock not returning ServiceResult", mock assertions failing, or type errors with...
勤怠システムの主要導線(ログイン→打刻→月次申請→承認→PDF出力)をE2Eで担保する。Playwrightでのテスト設計・実装・CI組込みに使う。
Test Textual TUI applications using the built-in testing framework. Covers headless mode testing with App.run_test(), complete Pilot API (mouse, keyboard, timing, animations), widget querying, and worker manage...
Comprehensive testing and quality assurance with Vitest unit/integration testing, Playwright E2E automation, and code coverage analysis. Supports TDD workflows, security testing, and CI/CD integration.
Use agent-browser CLI for UI testing - screenshots, element interaction, visual verification
Testing skill for Treido (typecheck, Vitest unit tests, Playwright e2e smoke). Triggers on "TEST:" prefix, failing tests, adding tests, or e2e stabilization work.
Execute a complete bugfix workflow for wouterwisse.com using Opus subagents. Investigates root cause, implements fix, and verifies no regressions.
Create TDD runbook with RED/GREEN/REFACTOR cycles from design document
Expert QA engineer for PayU Digital Banking Platform - specializing in comprehensive testing strategies, automation, performance, and financial compliance verification.
TDD(テスト駆動開発)のRed-Green-Refactorサイクルでコードを「実装」する。「エンティティ」「サービス」「API」「機能」の実装時に使用。「テスト駆動」「TDD」で品質を担保する。
Guide human PO through manual acceptance testing. Optional - use when PO wants manual verification before merge.
Guide for testing Shopify Apps, including Unit Testing with Remix, Mocking Shopify Context, and E2E Testing.
Plan cross-device automated tests.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Author OpenAPI/AsyncAPI specs, contracts, and mocks.
Visual regression testing for Bubble Tea TUI applications. This skill should be used when testing terminal UI appearance, capturing TUI screenshots, comparing visual output against golden files, or detecting UI...
Comprehensive code review with failure scenario analysis, security checks, and prioritized fix suggestions. Use after /execute to validate implementation quality.
Review code for implementation correctness, scalability, and production readiness. Use when reviewing PRs, auditing code quality, checking for performance issues, or evaluating production readiness. Triggers on...
Expert knowledge for testing FilamentPHP 4.x resources, tables, schemas, actions, and notifications using Pest and Livewire. Use this skill when writing or debugging tests for FilamentPHP components, implementi...
Check code coverage using Codecov MCP server. Use when user asks to check coverage, find untested code, compare branch coverage, review PR coverage impact, or identify files needing tests. Triggers on phrases l...
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.