testing
630
scala-cli-integration-tests
Add or run Scala CLI integration tests. Use when adding integration tests, debugging RunTests/CompileTests/etc., or working in modules/integration.
VirtusLab
testing-security
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
code-quality
629
fontsutil-font-usage
Use when modifying EasyPostman Swing UI fonts, especially when dialogs, labels, tables, tabs, or renderers look too large or too small, or when a change is about font size consistency with the user's configured UI font size. Prefer FontsUtil.getDefaultFontWithOffset(...) over hard-coded point sizes.
lakernote
testing-security
code-quality
629
swing-flatlaf-miglayout-principles
Use when modifying EasyPostman Swing forms that use FlatLaf and MigLayout, especially when layout refactors introduce clipped focus rings, dense spacing, border conflicts, or inconsistent form structure.
lakernote
testing-security
testing
629
swing-ui-test-headless-guard
Use when adding or updating EasyPostman Swing/TestNG UI tests that may run in headless CI. Extract and reuse the shared skip logic from AbstractSwingUiTest instead of duplicating DISPLAY/headless checks in each test.
lakernote
testing-security
testing
628
reaparr-backend-integration-tests
Use when creating, updating, debugging, or stabilizing Reaparr backend integration tests under tests/IntegrationTests, especially when failures involve async jobs, seeded data, fake Plex responses, filesystem behavior, or end-to-end API and database state validation.
Reaparr
testing-security
testing
628
reaparr-backend-unit-tests
Use when creating or updating C# backend unit tests in Reaparr, especially for handlers, services, endpoints, and jobs that must follow the project's TUnit, Shouldly, Moq, BaseUnitTest, naming, placement, and deterministic test-data conventions.
Reaparr
testing-security
code-quality
626
verification
Use when about to claim work is complete, a chapter is finished, or references are verified - requires running verification commands and confirming output before making any success claims
Norman-bury
testing-security
code-quality
626
writing-core
Use when writing STEM papers - enforces de-AI-ification rules, formatting standards, and quality controls
Norman-bury
testing-security
testing
622
testing-patterns
Patterns for testing code effectively. Use when breaking dependencies for testability, adding tests to existing code, understanding unfamiliar code through characterization tests, or deciding how to structure tests. Covers seams, dependency injection, test doubles, and safe refactoring techniques from Michael Feathers.
joelhooks
testing-security
security
620
ai-truthfulness-enforcer
MANDATORY verification system that prevents Claude Code instances from making false claims or fabricating evidence. Enforces cryptographic verification, real testing evidence, and automatic claim validation before any success statements can be made.
ananddtyagi
testing-security
code-quality
620
happier-testing
Repo-specific TDD and test-validation workflow for Happier changes, with lane selection, fixture policy, and anti-flake guardrails.
happier-dev
testing-security
code-quality
619
stacks-lint
Use when linting or formatting code in a Stacks project. CRITICAL - always use pickier, NEVER eslint directly. Run 'bunx --bun pickier .' to lint, 'bunx --bun pickier . --fix' to auto-fix. For unused variables, prefer eslint-disable-next-line comments over underscore prefix. Covers @stacksjs/lint and config/lint.ts.
stacksjs
testing-security
testing
619
stacks-faker
Use when working with fake data generation in a Stacks application — seeding databases, generating test data, model factories, or using faker utilities. Covers @stacksjs/faker (wrapper around ts-mocker) and its integration with the database seeder.
stacksjs
testing-security
testing
619
stacks-testing
Use when writing or running tests in Stacks — test setup, database test utilities (setup, refresh, truncate), DynamoDB testing, feature test patterns, the test CLI commands, test configuration in bunfig.toml, or test environment setup. Covers @stacksjs/testing and tests/.
stacksjs
testing-security
testing
619
stacks-validation
Use when implementing validation in Stacks — type guards (isString, isNumber, isBoolean, isObject, isArray, isFunction, etc.), numeric checks (isPositive, isEven, isInteger), the schema builder for model attribute validation, or request validation. Covers @stacksjs/validation.
stacksjs
testing-security
testing
618
react-testing
React component testing patterns including components, hooks, context, and forms. Covers Vitest Browser Mode with vitest-browser-react (preferred) and @testing-library/react. Use when testing React applications. For general UI testing patterns, see the front-end-testing skill.
citypaul
testing-security
testing
618
front-end-testing
Behavior-driven UI testing patterns. Covers Vitest Browser Mode (preferred) and DOM Testing Library. Use when testing any front-end application, writing UI tests, querying DOM elements, or simulating user interactions. For React-specific patterns, see the react-testing skill.
citypaul
testing-security
code-quality
618
typescript-strict
TypeScript strict mode patterns including schema-first development, branded types, type vs interface guidance, and tsconfig strict flags. Use when writing TypeScript code, defining types or schemas, or reviewing type safety. For immutability and pure function patterns, see the functional skill.
citypaul
testing-security
testing
618
mutation-testing
Mutation testing patterns for verifying test effectiveness. Use when analyzing branch code to find weak or missing tests.
citypaul
testing-security