add-testslisted

> **Script path fallback**: qq scripts are invoked as bare commands (e.g. `unity-test.sh`). If "command not found", use `${CLAUDE_PLUGIN_ROOT}/bin/<command>` instead. Respond in the user's preferred language (detect from their recent messages, or fall back to the language setting in CLAUDE.md). Add or update Unity tests for the current change. This skill is for **writing tests**, not for running them. After authoring coverage, hand off to `/qq:test`. > **Querying live scene/component state while authoring tests**: if you need to inspect the current Unity scene to understand what to assert (component layouts, serialized values, runtime state), see [`shared/tykit-reference.md`](../../shared/tykit-reference.md). Tools like `unity_query`, `unity_object`, `get-field`, `call-method`, `get-array` let you probe the live editor instead of guessing from source code. Arguments: $ARGUMENTS - A file path, symbol, bug description, or plan step that needs coverage - `editmode` / `edit`: force EditMode coverage - `playmode` / `play`: force PlayMode coverage - `regression`: force the smallest regression-focused test - `--assembly "Asm.Tests"`: prefer a specific test assembly - `--auto`: skip prompts and continue into `/qq:test --auto` after tests are written ## 0. Read qq project state first when available If `qq-project-state.py` is available, read it before choosing scope: ```bash qq-project-state.py --pretty ``` Use it for: - `work_mode` and `policy_profile` to understand expected