testing-preferred-patterns

What problem does it solve?

This Skill reduces test flakiness and brittleness by finding testing mistakes like flaky timing, order dependence, over-mocking, and incomplete assertions so your suite produces trustworthy evidence instead of false confidence.

Core Features & Use Cases

• Detects test quality failures: scans test code and classifies issues such as implementation-detail assertions, brittle selectors, skipped/ignored failures, incomplete assertions, and slow or flaky execution patterns.
• Prioritizes the highest-impact defects: ranks findings with HIGH for flaky and order-dependent tests, then guides fixes one pattern at a time to preserve intent.
• Guides evidence-based verification: recommends fixing tests to assert observable behavior and rerunning suites to confirm deterministic results.
• Use Case: A Go or JS/TS project has CI failures that are hard to reproduce locally; use this Skill to identify root quality smells (e.g., time.Sleep-based waits, over-mocked setups, or skipped tests) and turn them into deterministic, behavior-focused tests.

Quick Start

Use the testing-preferred-patterns skill to audit the target failing test file for flaky, brittle, and skipped test patterns, then apply one targeted pattern fix and rerun the suite until everything passes.