Discover documentation testing skills, compare source repositories and read the instructions for each workflow.
Detects non-functional "theater" code that appears complete but doesn't actually work. Use this skill to identify code that looks correct in static analysis but fails during execution, preventing fake implement...
Explain Cairo test organization for unit vs integration tests, tests directory layout, and shared helpers; use when a request involves structuring tests across files or crates in Cairo.
Explain how to test Starknet components by embedding them into mock contracts and dispatching calls; use when a request involves unit tests for component logic in Cairo.
Guides Claude through testing Gleam applications with gleeunit. Use when writing unit tests, integration tests, or property-based tests. Always use let assert, NOT deprecated should module.
Diagnose and fix common snforge test errors including Sierra compilation failures, cost computation cycles, and version mismatches; use when tests fail with cryptic errors even though `scarb build` succeeds.
Explain how to write and run Cairo tests, including `#[test]`, assert macros, `#[should_panic]`, `#[ignore]`, and `#[available_gas]`; use when a request involves writing or running unit tests in Cairo.
Validates that code actually works through sandbox testing, execution verification, and systematic debugging. Use this skill after code generation or modification to ensure functionality is genuine rather than...
Validates that code actually works through sandbox testing, execution verification, and systematic debugging. Use this skill after code generation or modification to ensure functionality is genuine rather than...
Use when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing, iterating until bulletproof aga...
Comprehensive Go testing patterns including table-driven tests, mocking, integration testing, benchmarks, and test organization.
A demo skill for testing OmniDev fixture integration
Testing patterns, 99% pass rate target, strategic skips, and E2E workflows
Take UI screenshots using Playwright and attach them as PR comments. Use this skill to capture visual state of UI components for code review, visual regression testing, or documentation.
Use when writing tests, verifying functionality, QA, test scenarios, user testing, or browser automation tests
Autonomous browser control with Cowork-style skill recording. Use when user requests "control my screen", "record workflow", "verify Lovable", "test scrapers", "debug DOM", "autonomous testing", or any browser...
指示された内容、または GitHub Pull Request で実装している内容に対して、 Playwright MCP, Playwright テストコードを生成および実行します。
Before submitting code or creating a Pull Request, when about to claim that work is complete, fixed, or passed, you must run verification commands and confirm the output results before making any success claims...
Before submitting code or creating a Pull Request, when about to claim that work is complete, fixed, or passed, you must run verification commands and confirm the output results before making any success claims...
Build and test premium UI components.
You are a data-driven and insightful Test Results Analyzer. You are an expert at looking at the output of large, automated test suites, identifying patterns, and triaging failures. You help the engineering team...
You are a detail-oriented and methodical API Tester. You are an expert at testing the functionality, reliability, performance, and security of APIs. You are proficient with tools like Postman, Insomnia, and aut...
TDD workflows, test generation, and coverage strategies with Claude Code. Use when writing tests, implementing TDD, analyzing coverage gaps, or generating quality unit/integration/e2e tests. Covers Jest, Vitest...
Comprehensive QA and testing skill for quality assurance, test automation, and testing strategies for ReactJS, NextJS, NodeJS applications. Includes test suite generation, coverage analysis, E2E testing setup,...
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.