vitest
Vitest testing framework patterns for test setup, async testing, mocking with vi.*, snapshots, and test performance (formerly test-vitest). This skill should…
Skills
Find an Agent Skill for your task. Read the guide and copy the install command.
Updated 10-24 00:15
Testing & quality
12,615 results
Playwright Browser Automation
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check…
rhdh-smoke-tests
Walks RHDH smoke tests: inspect plugin-catalog-index OCI refs first, then Helm and Operator in parallel (one namespace each): install the previous GA, upgrade…
ruview-verify
Verify a RuView build — full Rust workspace tests, the deterministic Python pipeline proof (SHA-256 Trust Kill Switch), firmware hash manifest, and the ADR-028…
vscode-tdd-expert
This skill provides expert-level guidance for Test-Driven Development (TDD) in VS Code extension development following t-wada methodology. Use when writing…
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing…
moq
Mocks dependencies in unit tests using Moq framework. Use when: writing unit tests, creating test doubles for interfaces, verifying method calls, mocking async…
playwright
Develops end-to-end UI tests with Playwright for Blazor applications. Use when: Writing E2E tests, testing Blazor WASM pages, validating UI flows, checking…
sorcha-ui
Builds Sorcha.UI Blazor WASM pages with accompanying Playwright E2E tests using the Docker test infrastructure. Use when: Working on Sorcha.UI, building new…
implementation-spec
Create an accepted, temporary implementation specification from settled software design before implementation begins. Use explicitly when the work needs a…
testing
Comprehensive test writing, execution, and failure analysis. Creates unit tests, integration tests, property-based tests, and benchmarks. Analyzes test…
xunit-testing-patterns
Master xUnit testing patterns for ABP Framework applications including unit tests, integration tests, test data seeders, and mocking strategies. Use when: (1)…
ameba-configuration
Use when configuring Ameba rules and settings for Crystal projects including .ameba.yml setup, rule management, severity levels, and code quality enforcement.
graphql-inspector-validate
Use when validating GraphQL operations/documents against a schema, checking query depth, complexity, or fragment usage.
pytest-advanced
Use when advanced Pytest features including markers, custom assertions, hooks, and coverage configuration.
rspec-advanced
Use when advanced RSpec features including custom matchers, shared examples, metadata, and hooks.
rspec-fundamentals
Use when rSpec fundamentals including describe, context, it blocks, let, and basic matchers for BDD testing.
adversarial-code-review
Review code through hostile perspectives to find bugs, security issues, and unintended consequences the author missed. Use when reviewing PRs, auditing…
migrate-to-shoehorn
Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial…
code-reviewer
Code review. Triggers: review, audit, check, take a look, any issues, security.
testing-production
Production validation specialist ensuring applications are fully implemented and deployment-ready. Use to verify no mock/stub/fake implementations remain,…
doc-sys-audit
Unified SYS audit wrapper that runs validator then reviewer and produces a combined report for fixer consumption
ftp-pentesting
FTP service (port 21) penetration testing methodology. Covers FTP service discovery and version identification, anonymous login testing, directory traversal and file download, credential brute-forcing, known vulnerability exploitation (vsftpd backdoor, ProFTPD, etc.), FTP Bounce attack. When an Agent scan finds port 21 open, needs to test FTP anonymous access, enumerate FTP file contents, or exploit FTP...
imap-pentesting
IMAP email service (ports 143/993) penetration testing methodology. Covers IMAP service discovery, banner information extraction, credential brute-forcing, mailbox enumeration and email download, IMAP command injection, and known vulnerability exploitation. When an Agent scan discovers that port 143 or 993 is open, and it is necessary to test IMAP authentication strength, enumerate mailbox contents, or exploit IMAP service vulnerabilities, this is triggered…