Total 50,473 skills, Testing & QA has 1779 skills
Showing 12 of 1779 skills
Test coverage analysis, identify gaps, and generate missing tests to achieve over 80% coverage. Trigger conditions: user requests for test coverage analysis, test coverage improvement, and test writing.
Use when writing any code - enforces test-driven development discipline with RED-GREEN-REFACTOR cycle, fires during any coding task
Red-green-refactor discipline. Use when writing new functionality.
Reviews the feature you just built and adds missing test coverage. Focuses on behavior that matters — not coverage metrics. Use after completing a feature to identify untested code paths, edge cases, and risk areas.
Review implementation quality — catch visual bugs, placeholder text, broken links, and spec drift that functional tests miss. Use this after tests pass to ensure the output looks right, not just works right.
Testing practices for iOS 26 / Swift 6.2 clinic modular MVVM-C applications. Covers unit/UI/snapshot testing, protocol-based mocks, async actor isolation, and dependency-injected test architecture aligned with Domain protocols, App-target composition, and Data-owned I/O boundaries. Use when writing, reviewing, or refactoring tests for ios-* and swift-* clinic modules.
Use when implementing features with test-driven development, writing tests before code, building domain-rich business logic, or following hexagonal architecture
Coverage-guided fuzzing workflow for C/C++, Rust, and Go targets. Runs audit-context-building to find suspicious code, writes a targeted harness, builds with sanitizers, runs the fuzzer, and reports crashes.
Points to Impersonator (EVM) and Impersonator Solana—open-source tools to connect to dApps via WalletConnect (and related flows) while presenting an arbitrary address for UI exploration without holding that address’s keys. Use when the user names impersonator.xyz, solana.impersonator.xyz, or the GitHub repos for local dev—not for phishing, identity fraud, or circumventing dApp or legal controls.
Use when you need framework-agnostic WireMock guidance — stub design, JSON or programmatic mappings, precise request matching, response bodies and faults, classpath fixtures, isolation and reset between tests, verification of calls, dynamic ports and base URLs, and avoiding flaky stubs — without choosing Spring Boot, Quarkus, or Micronaut. Part of the skills-for-java project
This skill should be used when a QA engineer wants to test or verify a completed task, run through acceptance criteria, check Gherkin scenarios against the implementation, record pass/fail results, or sign off on a ticket before merge. Triggers on phrases like "verify task
Dry-run Stacks contract calls against mainnet state before broadcasting — catches errors, prevents wasted gas