test-on-change

Executes impacted unit and end-to-end Playwright tests for Wodbrains project changes.

1|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/jdconley/wodbrains --skill test-on-change
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-on-change
Source: https://github.com/jdconley/wodbrains/tree/main/.cursor/skills/test-on-change
Command: npx skills add https://github.com/jdconley/wodbrains --skill test-on-change

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that all tests impacted by code modifications are executed, guaranteeing the stability and correctness of new or changed features.

Core Features & Use Cases

  • Automated Test Execution: Runs relevant unit and end-to-end (Playwright) tests automatically.
  • Targeted Testing: Focuses on tests directly affected by recent code changes, saving time compared to full test suites.
  • Use Case: After updating the user authentication flow, this Skill will run all tests related to login, registration, and session management to confirm no regressions were introduced.

Quick Start

Execute the test-on-change skill to run all tests affected by your recent code modifications.

Frequently Asked Questions about test-on-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run tests affected by code changes using Vitest and Playwright?

You can execute impacted unit and E2E tests by running the test-on-change scripts, which automatically target Vitest for core logic and Playwright for UI testing based on recent modifications.

What is targeted testing and how does it save time compared to a full test suite?

Targeted testing isolates and runs only the unit and E2E tests directly impacted by your recent code changes, ensuring correctness while saving time compared to executing the full test suite.

Can I configure Playwright worker and web server ports for deterministic UI testing?

Yes, the test execution supports specific configurations for Playwright's worker and web server ports, and includes stubbing parse behavior to ensure deterministic UI testing.

Does this automated testing approach work for both unit and end-to-end tests?

Yes, the automated test execution supports both unit tests using Vitest for core logic and end-to-end UI tests using Playwright to verify the stability of changed features.

Why run only affected tests after updating an authentication flow?

Running affected tests after updating an authentication flow verifies that login, registration, and session management features remain stable and free from regressions without executing the entire suite.