Search

PythonReactSEOPDF

research testing AI Skills

Discover research testing skills, compare source repositories and read the instructions for each workflow.

Categories: research testing

Showing 625–648 of 4,437

research testing Clear filters

Browse skills

GitHub

e2e-testing

korallis

Write comprehensive end-to-end tests that verify complete user workflows, integration between components, and system behavior from user perspective using Playwright, Cypress, or similar frameworks. Use when tes...

GitHub

lading-optimize-validate

DataDog

Validates discovered bugs with reproducing tests and validates fixes with regression tests. Called by other skills when bugs are found during optimization hunting. Creates property tests (proptest) and Kani pro...

GitHub

testing

zoonk

Write tests following TDD principles. Use when implementing features, fixing bugs, or adding test coverage. Covers e2e, integration, and unit testing patterns.

GitHub

strict-enforcement

elb-pr

Use when running claudikins-kernel:verify, checking implementation quality, deciding pass/fail verdicts, or enforcing cross-command gates — requires actual evidence of code working, not just passing tests

GitHub

testing-prpm-cli

pr-pm

Use when testing PRPM CLI commands locally - provides build, environment setup, execution workflow, contract testing to verify documented behavior matches implementation, and comprehensive cross-format conversi...

GitHub

fixing-flaky-tests

rileyhilliard

Diagnose and fix tests that pass in isolation but fail when run concurrently. Covers shared state isolation and resource conflicts. References condition-based-waiting for timing issues.

GitHub

elasticity-lab

gtmagents

Use to run pricing elasticity experiments with consistent assumptions and guardrails.

GitHub

quality-gates

gtmagents

Use when establishing tests, monitoring, and incident response for analytics models.

GitHub

playwright-debugging

ed3dai

Use when Playwright scripts fail, tests are flaky, selectors stop working, or timeouts occur - provides systematic debugging approach for browser automation issues

GitHub

writing-good-tests

ed3dai

Use when writing or reviewing tests - covers test philosophy, condition-based waiting, mocking strategy, and test isolation

GitHub

playwright-patterns

ed3dai

Use when writing Playwright automation code, building web scrapers, or creating E2E tests - provides best practices for selector strategies, waiting patterns, and robust automation that minimizes flakiness

GitHub

property-based-testing

ed3dai

Use when writing tests for serialization, validation, normalization, or pure functions - provides property catalog, pattern detection, and library reference for property-based testing

GitHub

writing-skills

ed3dai

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...

GitHub

ln-510-test-planner

levnikolaevich

Orchestrates test planning pipeline (research → manual → auto tests). Coordinates ln-511, ln-512, ln-513. Invoked by ln-500-story-quality-gate.

GitHub

ln-630-test-auditor

levnikolaevich

Test suite audit coordinator (L2). Delegates to 5 workers (Business Logic, E2E, Value, Coverage, Isolation). Aggregates results, creates Linear task in Epic 0.

GitHub

ln-635-test-isolation-auditor

levnikolaevich

Test Isolation + Anti-Patterns audit worker (L3). Checks isolation (APIs/DB/FS/Time/Random/Network), determinism (flaky, order-dependent), and 6 anti-patterns.

GitHub

ln-140-test-docs-creator

levnikolaevich

Creates test documentation (testing-strategy.md + tests/README.md). Establishes testing philosophy and Story-Level Test Task Pattern. L2 Worker in ln-100-documents-pipeline workflow.

GitHub

ln-502-regression-checker

levnikolaevich

Worker that runs existing tests to catch regressions. Auto-detects framework, reports pass/fail. No status changes or task creation.

GitHub

ln-513-auto-test-planner

levnikolaevich

Plans automated tests (E2E/Integration/Unit) using Risk-Based Testing after manual testing. Calculates priorities, delegates to ln-301-task-creator. Worker for ln-510.

GitHub

ln-512-manual-tester

levnikolaevich

Performs manual testing of Story AC via executable bash scripts saved to tests/manual/. Creates reusable test suites per Story. Worker for ln-510.

GitHub

ln-404-test-executor

levnikolaevich

Executes Story Finalizer test tasks (label "tests") from Todo -> To Review. Enforces risk-based limits and priority.

GitHub

ln-500-story-quality-gate

levnikolaevich

Story-level quality orchestrator. Pass 1: code quality -> regression -> manual testing (fail fast). Pass 2: verify tests/coverage -> mark Story Done. Auto-discovers team/config.

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.

More filters

Popularity

Popular tags