What problem does it solve?
Writing appropriate, repo-conforming Unity tests for code changes is time-consuming and often requires switching between test authoring and test execution, leading to context switching and inconsistent test placement that breaks project conventions.
Core Features & Use Cases
- Intelligent Test Type Selection: Automatically chooses the right test kind (EditMode for pure logic, PlayMode for scene/behavior, regression for bug fixes) based on your input or project state, or lets you force a specific type.
- Repo-Conventional Test Placement: Reuses existing test files, fixtures, and assembly definitions, or creates minimal new test structures that match your project's existing layout to keep the test suite coherent.
- Use Case: After fixing a bug in a Unity MonoBehaviour's physics logic, use this skill to write a narrow PlayMode regression test that proves the bug stays fixed, placed in your existing test suite, without running the test yourself.
Quick Start
Use the add-tests skill to write EditMode tests for the PlayerController.cs file you just modified to cover its new movement logic.