domains / software-engineering / test-suite / test
The two skills share the name 'test' but perform completely different tasks. The first is a Unity-specific skill for running and managing Unity Test Runner jobs asynchronously via a specific API. The second is a general-purpose skill for writing test suites for uncommitted code changes in a repository, using git to determine scope and classifying files to choose testing strategies. They do not overlap in procedure, parameters, or domain logic.
| Repository | Path |
|---|---|
| Besty0728/Unity-Skills | SkillsForUnity/unity-skills~/skills/test/SKILL.md |
| jsmastery-pro/skills | skills/test/SKILL.md |
| Role | Repository | Path |
|---|---|---|
| peer | Besty0728/Unity-Skills | SkillsForUnity/unity-skills~/skills/test/SKILL.md |
| peer | jsmastery-pro/skills | skills/test/SKILL.md |
--- name: test description: Run Unity tests or write test suites for code changes --- ## Conflicts The two skills named 'test' in the input are for different domains and do not share a common procedure. 1. **Besty0728/Unity-Skills**: This skill is for running Unity Test Runner operations. It involves calling specific Unity API endpoints (e.g., `test_run`, `test_list`) and polling for results using `jobId`. 2. **jsmastery-pro/skills**: This skill is for writing test suites for code changes. It involves using `git` to find uncommitted files, classifying them (e.g., component, logic, api), and writing test files based on a `test-preferences.json` configuration. Because these skills serve entirely different purposes (running existing tests in a game engine vs. writing new tests for general code), they cannot be combined into a single coherent instruction without losing the specific logic of each. An agent should select the appropriate skill based on the context (Unity project vs. general code repository).