Unit Testing

Set up and maintain continuous integration and continuous deployment pipelines with GitHub Actions, GitLab CI, Jenkins, or similar tools to automate testing, building, and deployment. Use when configuring automated builds, setting up test automation, implementing deployment automation, creating release workflows, managing environment deployments, configuring build caching, implementing blue-green deployments, setting up rollback strategies, or automating the entire software delivery pipeline.

Creates assessments with varied question types (MCQ, code-completion, debugging, projects) alignedto learning objectives with meaningful distractors based on common misconceptions. Activate wheneducators design quizzes, exams, or tests measuring understanding; need questions at appropriatecognitive levels (Bloom's taxonomy); want balanced cognitive distribution (60%+ non-recall); orrequire rubrics for open-ended questions. Generates MCQs with diagnostic distractors, code-writingprompts, debugging challenges, and project-based assessments targeting deep understanding.

Generate measurable learning outcomes aligned with Bloom's taxonomy and CEFR proficiency levels for educational content.Use this skill when educators need to define what students will achieve, create learning objectivesfor curriculum planning, or ensure objectives are specific and testable rather than vague.This skill helps break down complex topics into progressively building learning goals with clearassessment methods and success criteria.

Use when jUnit fundamentals including annotations, assertions, and test lifecycle for Java testing.

Use when modern PHP features including typed properties, union types, match expressions, named arguments, attributes, enums, and patterns for writing type-safe, expressive PHP code with latest language improvements.

Use when nestJS testing with unit tests, integration tests, and e2e tests. Use when building well-tested NestJS applications.

Use automatically during development workflows when making claims about tests, builds, verification, or code quality requiring concrete evidence to ensure trust through transparency.

Use when mocha test structure, hooks, and async testing patterns for JavaScript testing.

Use when modifying, removing, or refactoring code that lacks test coverage. Emphasizes the danger of untested changes and the RGR workflow to add characterization tests before modifications.

Use when creating or modifying GitHub Actions workflow files. Provides guidance on workflow syntax, triggers, jobs, steps, and expressions for creating valid GitHub Actions workflows that can be tested locally with act.

Use when working with TestNG annotations, assertions, test lifecycle, and configuration for Java testing.

Use when pytest plugin ecosystem including pytest-cov, pytest-mock, and custom plugin development.

Use when working on Claude Code plugins (creating, modifying, testing, releasing, or maintaining) - provides streamlined workflows, patterns, and examples for the complete plugin lifecycle

Use when writing new functions, adding features, fixing bugs, or refactoring by applying TDD principles - write failing tests before implementation code, make them pass, then refactor.

Use when testing GitHub Actions workflows locally with act. Covers act CLI usage, Docker configuration, debugging workflows, and troubleshooting common issues when running workflows on your local machine.

Use when adding interaction testing to Storybook stories. Enables automated testing of component behavior, user interactions, and state changes directly in stories.

Use when managing test state and infrastructure with reusable Playwright fixtures and lifecycle hooks for efficient test setup and teardown.

Use when creating custom Ameba rules for Crystal code analysis including rule development, AST traversal, issue reporting, and rule testing.

Use when applying Behavior-Driven Development patterns including Given-When-Then structure, feature files, and acceptance criteria. Use when writing BDD-style tests and specifications.

Use when testing Effect code including Effect.gen in tests, test layers, mocking services, and testing error scenarios. Use for writing tests for Effect applications.