Unit Testing

Use this skill when creating comprehensive testing strategies for applications. Provides test planning templates, coverage targets, test case structures, and guidance for unit, integration, E2E, and performance testing. Ensures robust quality assurance across the development lifecycle.

Use after completing a Sea of Nodes chapter implementation, before marking the chapter issue as complete. Validates implementation against official tutorial by comparing node types, test coverage, and key concepts.

Create and maintain AgentV YAML evaluation files for testing AI agent performance. Use this skill when creating new eval files, adding eval cases, or configuring custom evaluators (code validators or LLM judges) for agent testing workflows.

Define technical specifications including tech stack, security, theme standards (from UX mockup), coding standards, and testing standards. Use when user asks to define tech specs, choose tech stack, or start Stage 7 after architecture.

Create, test, and package Helm charts for Kubernetes. Covers helm create, Chart.yaml,values.yaml, template development, chart dependencies, packaging, and repository publishing.Use when user mentions Helm charts, helm create, Chart.yaml, values.yaml, helm lint,helm template, helm package, or Kubernetes packaging.

Automatically creates comprehensive pull requests to the dev branch when user indicates their feature/fix is complete and ready for review. Use when user mentions creating PR, submitting for review, or indicates work is done. Examples - "create a PR", "ready for review", "open a pull request", "submit this to dev", "all tests passing, let's get this reviewed".

Follow established project structure, version control practices, documentation standards, and development workflows to maintain consistency across the team. Use this skill when organizing files and directories in a project. When writing README documentation or contributing guidelines. When creating git commits with clear messages or pull request descriptions. When managing environment configuration or dependencies. When setting up feature flags or maintaining changelogs. When establishing code review processes or testing requirements. This skill applies to all project management and development workflow tasks.

Debugs Buck2 build failures systematically by analyzing error logs, checking common issues (cache, visibility, cycles), and suggesting fixes. Use when builds fail, tests won't run, or Buck2 reports errors.

Enterprise-grade browser automation using WebDriver protocol. Use when the user needs to automate web browsers, perform web scraping, test web applications, fill forms, take screenshots, monitor performance, or execute multi-step browser workflows. Supports Chrome, Firefox, and Edge with connection pooling and health management.

WCAG 2.1/2.2 compliance implementation, ARIA patterns, keyboard navigation, focus management, and accessibility testing. Use when implementing accessible components, fixing accessibility issues, or when the user mentions WCAG, ARIA, screen readers, or keyboard navigation.

Test GitHub Actions workflows locally using act before pushing changes. Use when modifying .github/workflows files, before committing workflow changes, when debugging GitHub Actions failures, or when the user mentions testing workflows, act tool, or validating CI/CD changes.

Integration guide for SawyerHood/dev-browser, a Claude Code plugin for browser automation. This skill enables agents to research, test web UIs, and interact with web applications using a headless browser.

Code coverage for Rust using LLVM instrumentation with support for multiple output formats and CI integration.Use when measuring test coverage, generating coverage reports, enforcing coverage thresholds, or integrating with codecov/coveralls.Trigger terms: coverage, llvm-cov, code coverage, test coverage, coverage report, codecov, coveralls, branch coverage.

Check CI/CD status of a pull request including workflow runs and test results. Use when verifying if PR checks are passing or investigating CI failures.

Automated validation orchestration across proof, spec, type, contract, and test artifacts with configurable precedence and gating. This skill provides both reference documentation AND execution capabilities for the full PLAN -> CREATE -> EXECUTE -> REPORT workflow.

Create isolated jj workspaces for testing changes, running experiments in parallel, and exploring alternative implementations. Use when testing breaking changes, comparing different approaches, or running long-running operations without blocking other work. (project)

Use when user asks to "test skill invocation framework" or mentions "canary skill test". This is a self-test skill to verify the test framework correctly loads and invokes skills.

Vitest browser mode component testing. Use for testing Svelte 5 components with real browsers, locators, accessibility patterns, and reactive state.

This skill provides guidance for using Playwright MCP for browser automation. Use when navigating web pages, interacting with web elements, taking screenshots, filling forms, running browser tests, or automating any browser-based tasks.

Generate test coverage reports showing which code paths are tested. Use to identify untested code and improve test coverage.