mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios.git
synced 2026-10-16 09:58:36 +00:00
DonchitosandClaude Opus 5.5
be8993bbc5
Fix release for 1.1.2: the 14 longest skills keep their later phases after a compaction, a question nobody answered is never taken as an answer, settings read the same from a subfolder, the commit check works for a project in a subfolder of a larger repository, every skill opens with a title, and the shipped allow rules no longer approve deleting a branch or writing files without asking. Details in CHANGELOG.md; upgrade steps in UPGRADING.md (v1.1.2 → v1.1.3). Refs #83 Refs #133 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0185en4t76fPn7315q4c3nko
45 lines
1.6 KiB
Markdown
45 lines
1.6 KiB
Markdown
# /test-setup — Phase 2: Present Plan
|
|
|
|
> Part of `/test-setup`. `SKILL.md` names when to read this file; the settings it
|
|
> resolved and the rules under its later headings still apply here.
|
|
|
|
## Phase 2: Present Plan
|
|
|
|
Based on the engine detected and the existing state, present a plan:
|
|
|
|
```
|
|
## Test Setup Plan — [Engine]
|
|
|
|
I will create the following (skipping any that already exist):
|
|
|
|
tests/
|
|
unit/ — Isolated unit tests for formulas, state, and logic (Godot only)
|
|
integration/ — Cross-system tests and save/load round-trips (Godot only)
|
|
smoke/ — Critical path test list (15-minute manual gate)
|
|
README.md — Test framework documentation
|
|
|
|
[Unity/Unreal: unit and integration tests go under the engine's test root
|
|
instead — Unity Assets/Tests/EditMode|PlayMode/, Unreal
|
|
Source/<Module>/Private/Tests/ — because neither compiles code in tests/]
|
|
|
|
production/qa/
|
|
evidence/ — Screenshot and manual test sign-off records
|
|
|
|
[Engine-specific files — see per-engine details below]
|
|
|
|
.github/workflows/tests.yml — CI: run tests on every push to main
|
|
|
|
Estimated time: ~5 minutes to create all files.
|
|
```
|
|
|
|
Ask: "May I create these files? I will not overwrite any test files that
|
|
already exist at these paths."
|
|
|
|
**At `collaborative` and `guided`** — do not proceed without approval. These are
|
|
**new** files, and `automation-modes.md:81` gates new-file writes in `guided` too,
|
|
so the answer is the same in both modes. **At `autonomous`** — create them and log
|
|
the decision; do not block. An unconditional gate here would read as "block even
|
|
in autonomous" and contradict this skill's own header.
|
|
|
|
---
|