Loading...
Loading...
Found 146 Skills
Generate Jest unit tests for JavaScript/TypeScript with mocking, coverage. Use for JS/TS modules, React components, test generation, or encountering missing coverage, improper mocking, test structure errors.
Comprehensive TDD patterns and practices for all programming languages, eliminating redundant testing guidance per agent.
[AUTO-INVOKE] MUST be invoked BEFORE writing or modifying any test files (*.t.sol). Covers test structure, naming conventions, coverage requirements, fuzz testing, and Foundry cheatcodes. Trigger: any task involving creating, editing, or running Solidity tests.
Testing React Native. Use when writing tests, reviewing test coverage, or setting up testing.
Load PROACTIVELY when task involves writing tests, improving coverage, or test infrastructure. Use when user says "add tests", "write unit tests", "set up E2E testing", "improve coverage", or "add mocks". Covers Vitest/Jest unit tests, React Testing Library component tests, Playwright E2E tests, MSW API mocking, test organization and naming, fixture management, coverage targets and thresholds, snapshot testing, and CI integration.
This skill should be used when auditing a codebase for AI agent readiness, or when guiding improvements to make a codebase work well with agentic coding tools. It applies when users ask to evaluate test coverage, file structure, type system usage, dev environment speed, or automated enforcement -- the five pillars that determine how effectively coding agents can operate in a project. Triggers on "audit my codebase", "make this agent-ready", "improve for AI agents", "agent-friendly", or questions about why agents struggle with a codebase.
Combinatorial testing with a greedy pairwise matrix generator. Covers all factor pairs in near-minimal test cases.
Creates comprehensive test suites for Move contracts with 100% coverage requirement. Triggers on: 'generate tests', 'create tests', 'write test suite', 'test this contract', 'how to test', 'add test coverage', 'write unit tests'.
Review Dojo code for best practices, common mistakes, security issues, and optimization opportunities. Use when auditing models, systems, tests, or preparing for deployment.
Review Playwright tests for quality. Use when user says "review tests", "check test quality", "audit tests", "improve tests", "test code review", or "playwright best practices check".
Pull request and code review with diff-based routing across five dimensions: code quality and guideline compliance, test coverage analysis, silent failure detection, type design and invariant analysis, and comment quality auditing. Classifies changed files and loads only relevant review methodologies. Produces severity-ranked findings (Critical, Important, Suggestion) with confidence scoring. Replaces pr-review-toolkit plugin. Trigger phrases: "review my PR", "review this code", "check my changes", "is this ready to merge", "audit this PR", "review before committing", "check code quality", "any issues with this code", "pre-merge review", "look over my changes", "code review". Use this skill when reviewing code before commit or merge, checking PR quality, or when the user asks for feedback on recent modifications.
Review changes for test gaps, simplification, naming consistency, reuse opportunities, and TODO quality