Unit Testing

Runs tests and handles failures. Triggered when: test execution, verification, test failures, CI checks.

生成并配置用于新华三技术有限公司H3C网络设备自动化的 pytest `conftest.py`，`conftest.py`文件主要负责测试背景搭建和测试背景清理。

Automatically run the test suite when code changes are made to ensure all tests pass before proceeding. This skill runs pytest for backend projects and Playwright for frontend projects, and reports test results, coverage, and any failures.

Review HTML/CSS and React/TypeScript code for WCAG 2.1 Level AA accessibility compliance. Use when the user asks to review code for accessibility, check WCAG compliance, identify accessibility issues, or audit components/pages for a11y standards. Applicable for code reviews, component development, and accessibility testing.

Comprehensive testing workflow combining TDD, real implementations (no mocking), and E2E testing. Use when implementing features, writing tests, or setting up test infrastructure.

Build responsive layouts that adapt seamlessly across devices using mobile-first design, fluid layouts, and standard breakpoints. Use this skill when implementing responsive designs, creating mobile-first layouts, defining breakpoint styles, working with responsive components and pages, using relative units (rem, em) instead of fixed pixels, implementing media queries, ensuring touch-friendly tap targets, optimizing images and assets for different screen sizes, maintaining readable typography across breakpoints, prioritizing content for smaller screens, testing UI across mobile, tablet, and desktop devices, or building fluid container layouts. Apply this skill when building responsive UI components, optimizing layouts for different screen sizes, or reviewing mobile and tablet user experiences.

Evaluation and reporting for code quality, performance, security, architecture, team processes, AI/LLM outputs, A/B tests, ROI analysis, and compliance. Scoring systems, benchmarking, dashboard creation, and multi-format report generation (PDF, HTML, Markdown, JSON).

Four-phase debugging: root cause → patterns → hypothesis → implement. For complex bugs, test failures, multi-component issues. NOT for obvious syntax errors.

Apply private modules with public re-exports pattern for clean API design. Includes conditional visibility for docs and tests. Use when creating modules, organizing mod.rs files, or before creating commits.

Run Lighthouse audit and verify Core Web Vitals. Use at project end before release. Triggers on "performance", "Lighthouse", "Core Web Vitals", "speed test", "page speed".

Validates complete requirements traceability across EARS requirements → design → tasks → code → tests.Trigger terms: traceability, requirements coverage, coverage matrix, traceability matrix,requirement mapping, test coverage, EARS coverage, requirements tracking, traceability audit,gap detection, orphaned requirements, untested code, coverage validation, traceability analysis.Enforces Constitutional Article V (Traceability Mandate) with comprehensive validation:- Requirement → Design mapping (100% coverage)- Design → Task mapping- Task → Code implementation mapping- Code → Test mapping (100% coverage)- Gap detection (orphaned requirements, untested code)- Coverage percentage reporting- Traceability matrix generationUse when: user needs traceability validation, coverage analysis, gap detection,or requirements tracking across the full development lifecycle.

Use when tests have race conditions, timing dependencies, or inconsistent pass/fail behavior - replaces arbitrary timeouts with condition polling to wait for actual state changes, eliminating flaky tests from timing guesses

A skill for managing database migrations with Alembic. Use this for tasks involving Alembic initialization, configuration, creating new migration scripts (both autogenerated and manual), defining upgrade and downgrade logic, handling data migrations, testing migrations, performing rollbacks, and following production deployment best practices for database changes.

Workflow for private repos + Colab training. Trigger when: (1) training on Colab with private repo, (2) separating dev from production, (3) avoiding untested code in production.

Python 3.11+ development with type hints, async patterns, FastAPI, and pytest. Use for backend services, CLI tools, data processing, and API development.

Your approach to handling testing testing. Use this skill when working on files where testing testing comes into play.

Expert system for investigating CockroachDB test failures, especially KV failures.

Proactively suggests tests when code changes are detected. Activates when functions are created, logic is modified, security-sensitive code is added, or bug fixes are implemented. Provides non-intrusive test recommendations to help vibe coders ship with confidence.

Run and manage functional tests (unit, integration, E2E, mutation). Use when running tests, debugging test failures, ensuring test coverage, or fixing mutation testing issues. Covers PHPUnit, Behat, and Infection. For K6 load/performance tests, use the load-testing skill instead.

Validate Laravel database configuration and test actual connections. Use when user reports "database connection error", "hosts array is empty", "could not connect to database", or wants to verify database setup is correct.