testing
5.2K
frb-develop-feature
Use when adding tests or developing new features in flutter_rust_bridge, when compilation is slow, or when learning twin test naming conventions
fzyzcjy
testing-security
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
testing
5.2K
frb-fix-ci
Use when CI fails in flutter_rust_bridge - before deep investigation
fzyzcjy
testing-security
testing
5.1K
mooncake-ci-local
Run Mooncake CI test suite locally — maps GitHub Actions CI steps to local commands. Use this skill whenever the user wants to run tests locally, reproduce a CI failure, check if their changes break tests, or run any subset of the CI test suite (C++ unit tests via ctest, Python integration tests, code format checks, or the full test pipeline). Trigger on phrases like "run tests", "run CI locally", "reproduce CI failure", "check my changes", "test before PR", "run ctest", "run python tests", "run all tests".
kvcache-ai
testing-security
testing
5.1K
windows-mcp-tool-tester
Automated testing skill for Windows-MCP tools. Use this skill whenever the user wants to test, validate, benchmark, or evaluate any Windows-MCP tool (App, PowerShell, Screenshot, Snapshot, Click, Type, Scroll, Move, Shortcut, Wait, MultiSelect, MultiEdit, Clipboard, Process, Notification, FileSystem, Registry, Scrape). Triggers on phrases like "test the Click tool", "benchmark Screenshot", "validate FileSystem", "run QA on Registry", "check if PowerShell works", "evaluate tool performance", or any mention of testing/validating a Windows-MCP tool. Each invocation tests exactly ONE tool.
CursorTouch
testing-security
testing
5K
improve-ut
Analyzes changed files and improves unit test coverage using project-specific testing conventions from .trellis/spec/ unit-test specs. Determines test scope (unit vs integration vs regression), adds or updates tests following existing patterns, and runs validation. Use when code changes need test coverage, after implementing a feature, after fixing a bug, or when test gaps are identified.
mindfold-ai
testing-security
testing
5K
improve-ut
Analyzes changed files and improves unit test coverage using project-specific testing conventions from .trellis/spec/ unit-test specs. Determines test scope (unit vs integration vs regression), adds or updates tests following existing patterns, and runs validation. Use when code changes need test coverage, after implementing a feature, after fixing a bug, or when test gaps are identified.
mindfold-ai
testing-security
testing
5K
add-unit-tests
Guide for adding unit tests to AReaL. Use when user wants to add tests for new functionality or increase test coverage.
inclusionAI
testing-security
testing
5K
add-unit-tests
Guide for adding unit tests to AReaL. Use when user wants to add tests for new functionality or increase test coverage.
inclusionAI
testing-security
testing
5K
add-unit-tests
Guide for adding unit tests to AReaL. Use when user wants to add tests for new functionality or increase test coverage.
inclusionAI
testing-security
testing
5K
rstudio-create-playwright-tests
Complete guide for creating RStudio Playwright tests in TypeScript. Covers critical rules, stable selectors, code patterns, conventions, and review checklists. Use when writing, reviewing, or migrating Playwright tests for RStudio.
rstudio
testing-security
testing
5K
rstudio-run-playwright-tests
How to run RStudio Playwright tests in Desktop and Server modes. Use this skill whenever the user asks to run, execute, or launch Playwright tests against RStudio - whether on Desktop (local) or Server (remote). Also use when the user asks about the test command, environment variables, or how to point tests at a server URL. Trigger on phrases like "run the test", "execute on server", "run it on desktop", "run against <IP>", or any request involving npx playwright test for the RStudio test suite.
rstudio
testing-security
testing
4.9K
ci-readiness-check
Use when the user explicitly asks for a CI check or to push their branch — e.g. "ci readiness", "check ci", "pre-push check", "ready for CI", "ci check", "ready to push", "push my changes", "push the branch", "let's push". Catches common CI failures before pushing — formatting, stale API reports, missing changesets, policy violations.
microsoft
testing-security
testing
4.9K
finishing-a-development-branch
Use this when you have completed some feature implementation and have written passing tests, and you are ready to create a PR.
microsoft
testing-security
testing
4.9K
test-driven-development-tdd
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
microsoft
testing-security
testing
4.9K
testing-anti-patterns
Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies
microsoft
testing-security
testing
4.8K
playwright-app-testing
Test the Expensify App using Playwright browser automation. Use when user requests browser testing, after making frontend changes, or when debugging UI issues
Expensify
testing-security
testing
4.8K
control-api-tests
Instructions for writing unit tests for new public APIs on WinForms controls and components. Covers test project structure, naming conventions, property tests, event tests, OnXxx method tests, SubControl patterns, data attributes, and handle-state verification.
dotnet
testing-security
testing
4.8K
gdi-rendering-tests
Instructions for writing unit tests for Graphics, Bitmap, GraphicsPath, and Font rendering APIs in System.Drawing. Covers bitmap-based verification, integer/float overload testing, version-guarded test blocks, and FluentAssertions patterns for path-point validation.
dotnet
testing-security
testing
4.8K
kotest
Helps write, migrate, and improve Kotlin tests using the Kotest testing framework. Covers test spec styles (FunSpec, DescribeSpec, BehaviorSpec, etc.), assertions (shouldBe, matchers, soft assertions), property-based testing (Arb, forAll, checkAll), data-driven testing, lifecycle hooks, extensions, coroutine testing, project configuration, and multiplatform setup. Use when the user mentions Kotest, kotest matchers, property testing with Arb, Kotest spec styles, shouldBe assertions, Kotlin test framework, or migrating from JUnit/TestNG/Spek to Kotest.
kotest
testing-security
testing
4.7K
clawteam-dev
Use this skill when working inside the ClawTeam repository itself: local development, debugging, reviewing, testing, validating multi-agent flows, or checking whether a code change actually works end-to-end. Use the repository bootstrap scripts to standardize the local `clawteam` command and to wire project-local `.agents` and `.claude` skills back to this repository. This skill is repository-development oriented, not a general end-user usage guide.
HKUDS
testing-security
testing
4.6K
write-backend-unit-test
Write or update Baserow backend tests for core, premium, or enterprise code using pytest, Django, DRF APIClient, and the repo's shared fixture patterns.
baserow
testing-security
testing
4.6K
write-frontend-unit-test
Write or update Baserow frontend unit tests for core, premium, or enterprise code using the repo's existing Vitest, Nuxt, Vue Test Utils, TestApp, and snapshot patterns.
baserow
testing-security
