testing
403
run-unit-tests
Build and run dxvk-remix unit tests. Use when the user asks to run tests, add new tests, or verify that code changes pass existing tests.
NVIDIAGameWorks
testing-security
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
testing
403
add-assertion
Add new assertion function with comprehensive tests following TDD
TypedDevs
testing-security
testing
403
check-coverage
Analyze test coverage and identify untested code paths
TypedDevs
testing-security
testing
399
debug-surefire
Debug Maven Surefire unit tests by running them in JDWP "wait for debugger" mode (`-Dmaven.surefire.debug`) and attaching to the forked test JVM using **jdb** (preferred for CLI/agent debugging), IntelliJ, or VS Code. Use when asked to debug/step through a failing JUnit test, attach a debugger to a Maven test run, or run `mvn test -Dtest=Class[#method]` suspended on a port (including multi-module `-pl` runs). The JVM will block at startup until a debugger attaches; the agent should attach with `jdb -attach <host>:<port>` and drive the session from the terminal.
eclipse-rdf4j
testing-security
testing
393
update-flaky-tests
Update the flaky test tracker. Use when you encounter test failures unrelated to your current work, after committing a fix for a known flaky test, or to check flaky test status.
platformplatform
testing-security
testing
392
mvnf
Run Maven tests in this repo with a consistent workflow (module clean, root -Pquick clean install to refresh .m2_repo, then module verify or a single test class/method). Use when asked to run tests/verify in the rdf4j multi-module build or when the user says mvnf.
eclipse-rdf4j
testing-security
testing
388
tests-standards
Write focused tests for core user flows and critical paths with clear test names, behavior-focused assertions, mocked external dependencies, and fast execution, deferring edge case testing until explicitly required. Use this skill when creating or modifying test files, writing unit tests, integration tests, or test cases for any feature. Apply when writing test files (test/, __tests__/, spec/, .test.js, .spec.ts, test_*.py), implementing tests for core user workflows, testing critical business logic, mocking external dependencies (databases, APIs, file systems), writing descriptive test names, creating fast-running unit tests, or adding tests at logical completion points of feature development. Use for any task involving test creation, test coverage, test strategy, or test-driven development.
maxritter
testing-security
testing
388
testing-standards
Prevent common testing anti-patterns that undermine test effectiveness and code quality by ensuring tests verify real behavior rather than mock behavior, keeping production code free from test-only pollution, and enforcing thoughtful mocking strategies. Use this skill when writing or modifying any test files (.test.ts, .test.js, .spec.ts, _test.py, test_*.py, *_test.go, *_spec.rb), when adding mock objects, stubs, spies, or test doubles to test suites, when considering adding methods or properties to production classes that are only called from test code, when setting up complex test fixtures or test data, when tests are failing and you're tempted to adjust mocks to make them pass, when deciding how to isolate code under test from external dependencies, when implementing dependency injection or test seams, during code reviews when reviewing test implementation and mocking strategies, when refactoring tests that have become brittle or hard to maintain, when test setup code is becoming longer than the actual te
maxritter
testing-security
testing
376
real-pytest-no-mocks-real-tests
Write pytests that test real public interfaces with actual components, no mocking, and precise assertions. MIRA-specific patterns. Use when creating or reviewing tests.
taylorsatula
testing-security
testing
358
playwright-testing
This skill should be used when user asks about "Playwright", "responsiveness test", "test with playwright", "test login flow", "file upload test", "handle authentication in tests", or "fix flaky tests".
fcakyon
testing-security
testing
318
skill-with-frontmatter
A test skill with full YAML frontmatter for testing frontmatter parsing
kasperjunge
testing-security
testing
313
testing-strategy
Use when writing tests, reviewing test code, or discussing testing approach for walkerOS packages. Covers env pattern, dev examples, and package-specific strategies.
elbwalker
testing-security
testing
310
go-table-driven-tests
Write Go table-driven tests following Go community best practices and this repository's conventions. Use when writing or refactoring Go tests, especially when you notice repeated test patterns or copy-pasted test code.
Xe
testing-security
testing
304
qa-planning
Generate QA Contract with numbered Gherkin scenarios (G#N) and acceptance criteria (AC#N)
WellApp-ai
testing-security
testing
304
test-hardening
Convert passed QA Contract criteria to automated tests
WellApp-ai
testing-security
testing
304
webapp-testing
Test web app UI using Browser MCP and Storybook
WellApp-ai
testing-security
testing
301
ark-chainsaw-testing
Run and write Ark Chainsaw tests with mock-llm. Use for running tests, debugging failures, or creating new e2e tests.
mckinsey
testing-security
testing
240
temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.
benchflow-ai
testing-security
testing
211
dependency-check
Check for required dependencies (Chrome DevTools MCP, OpenRouter API) before running commands that need them. Use at the start of /implement, /review, /validate-ui commands to provide helpful setup guidance.
MadAppGang
testing-security
testing
208
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first
brobertsaz
testing-security