Testing
Unit tests, integration tests, test automation
test-analysis-extensions
by dotnet
Provides file paths to language-specific reference files for the test ANALYSIS skills (assertion-quality, test-anti-patterns, test-gap-analysis, test-smell-detection, test-tagging). Call this skill to discover available extension files (e.g., dotnet.md for .NET/MSTest/xUnit/NUnit/TUnit, python.md for pytest/unittest, typescript.md for Jest/Vitest/Mocha, java.md for JUnit/TestNG, etc.). Do not use directly — invoked by the test-quality-auditor agent and polyglot analysis skills that need framework-specific lookup tables (test markers, assertion APIs, skip annotations, sleep patterns, mystery guest indicators, integration markers, setup/teardown, tag-support capability).
test-tagging
by dotnet
"Analyzes test suites in any language and tags each test with standardized traits (positive, negative, critical-path, boundary, smoke, regression, integration, performance, security). Use when the user wants to categorize, audit, or label tests with traits. Works across .NET (MSTest/xUnit/NUnit/TUnit), Python (pytest), TS/JS (Jest/Vitest), Java, Go, Ruby, Rust, Swift, Kotlin, PowerShell, and C++ — auto-editing when the framework has canonical tag syntax, otherwise report-only. Do not use for writing new tests, running tests, or migrating frameworks."
code-testing-agent
by dotnet
Generate or add unit tests for existing code, from one function to a project-wide suite. ALWAYS USE for "write/add/generate tests", "cover this untested method", scaffolding tests where none exist, or comprehensive suites. Polyglot; supports classic packages.config MSTest, sparse workspaces, and proportional focused work. DO NOT USE for only running/diagnosing tests, coverage/audits, or correcting supplied MSTest assertions, attributes, lifecycle, or configuration without designing new cases (writing-mstest-tests).
assertion-quality
by dotnet
"Produce an assertion-quality report or metrics for existing tests. ALWAYS USE when asked whether assertions are weak, shallow, trivial, always true, self-referential, or diverse; which tests are assertion-free or use only presence/truthiness checks; or for depth/variety metrics. Polyglot. DO NOT USE for direct fixes: use writing-mstest-tests for supplied MSTest assertions, or code-testing-agent when new cases must be designed. Do not use for mutation reasoning (test-gap-analysis) or a general severity-ranked audit (test-anti-patterns)."
filter-syntax
by dotnet
"Reference data for test filter syntax across all platform and framework combinations: VSTest --filter expressions, MTP filters for MSTest/NUnit/xUnit v3/TUnit, and VSTest-to-MTP filter translation. DO NOT USE directly — loaded by run-tests, mtp-hot-reload, and migrate-vstest-to-mtp when they need filter syntax."
microbenchmarking
by dotnet
Activate this skill when BenchmarkDotNet (BDN) is involved in the task — creating, running, configuring, or reviewing BDN benchmarks. Also activate when microbenchmarking .NET code would be useful and BenchmarkDotNet is the likely tool. Consider activating when answering a .NET performance question requires measurement and BenchmarkDotNet may be needed. Covers microbenchmark design, BDN configuration and project setup, how to run BDN microbenchmarks efficiently and effectively, and using BDN for side-by-side performance comparisons. Do NOT use for profiling/tracing .NET code (dotnet-trace, PerfView), production telemetry, or load/stress testing (Crank, k6).
testing
by EpicenterHQ
Test file conventions for setup functions, factory patterns, test organization, type testing, and naming. Use when writing or modifying *.test.ts files, creating test setup functions, or reviewing test structure.
Components
by HoangNguyen0403
Standards for Standalone Components, Signals inputs, and Control Flow.
Android Testing
by HoangNguyen0403
Standards for Unit Tests, UI Tests (Compose), and Hilt Integration
Android Legacy State
by HoangNguyen0403
Standards for State integration with Views using Coroutines and Lifecycle
Android Background Work
by HoangNguyen0403
Standards for WorkManager and Background Processing
Testing
by HoangNguyen0403
Standards for Component Test Harnesses and TestBed.
tdd
by Yeachan-Heo
Test-Driven Development enforcement skill - write tests first, always
ralph
by Yeachan-Heo
Self-referential loop until task completion with architect verification
configure-notifications
by Yeachan-Heo
Configure notification integrations (Telegram, Discord, Slack) via natural language
ultrapilot
by Yeachan-Heo
Parallel autopilot with file ownership partitioning
ultraqa
by Yeachan-Heo
QA cycling workflow - test, verify, fix, repeat until goal met
resolve-conflicts
by antinomyhq
Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.
create-pr-description
by antinomyhq
Generate and create pull request descriptions automatically using GitHub CLI. Use when the user asks to create a PR, generate a PR description, make a pull request, or submit changes for review. Analyzes git diff and commit history to create comprehensive, meaningful PR descriptions that explain what changed, why it matters, and how to test it.
testing-python
by PrefectHQ
Write and evaluate effective Python tests using pytest. Use when writing tests, reviewing test code, debugging test failures, or improving test coverage. Covers test design, fixtures, parameterization, mocking, and async testing.
testing-standards
by DaveSkender
Testing conventions for Stock Indicators. Use for test naming (MethodName_StateUnderTest_ExpectedBehavior), FluentAssertions patterns, precision requirements, and test base class selection.
cts-triage
by gfx-rs
Run CTS test suites and investigate failures
webgpu-specs
by gfx-rs
Download WebGPU and WGSL specifications for use as a reference
write-tests
by elie222
Write focused unit tests for backend and utility logic