ksh999000/Claude-Code-Game-Studios
1
0
Fork 0
mirror of https://github.com/Donchitos/Claude-Code-Game-Studios.git synced 2026-10-16 10:17:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

Release 1.1.3 — long skills keep their later steps

Browse Source 
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
This commit is contained in:
Donchitos
2026-10-08 17:52:48 +11:00
co-authored by Claude Opus 5.5
parent b21fa0f7f2
commit be8993bbc5
231 changed files with 12000 additions and 10527 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.claude/skills/start/SKILL.md
+9 -4
View File
@@ -174,7 +174,7 @@ In `project.yaml`, ensure a `project:` block exists with `stage: [value]`.
schema_version: 1
framework:
version: 1.1.2
version: 1.1.3
last_upgraded: <YYYY-MM-DD>
project:
@@ -249,8 +249,11 @@ Value mapping (ignore any ` (Recommended)` suffix on the first option):
Write `modes.rigor` to `project.yaml` immediately after the user selects — no
separate "May I write?" needed, as the write is a direct consequence of the
selection. Use the Edit tool to add it under the `modes:` block. There is **no
legacy mirror file** for this setting, so this is a single write, not a dual-write.
selection. Use the Edit tool. The Phase 3c template has no `modes:` block: if
`project.yaml` has none, add one with `rigor:` under it; if it has one, add
`rigor:` under it. Never add a second `modes:` line — YAML allows one block per
key. There is **no legacy mirror file** for this setting, so this is a single
write, not a dual-write.
If the Phase 3c `project.yaml` write was declined, do not write this one either —
carry the answer forward and say it was not saved.
@@ -288,7 +291,9 @@ Value mapping: `Collaborative` → `collaborative`, `Guided (recommended)` →
Write `modes.automation` to `project.yaml` immediately after the user selects —
no separate "May I write?" needed, as the write is a direct consequence of the
selection. Use the Edit tool to add it under the `modes:` block. There is **no
selection. Use the Edit tool to add `automation:` under the `modes:` block
(Phase 3d creates it); if `project.yaml` has none, add one.
Never add a second `modes:` line — YAML allows one block per key. There is **no
legacy mirror file** for this setting. If the Phase 3c `project.yaml` write was
declined, do not write this one either — say it was not saved.