ksh999000/Claude-Code-Game-Studios
1
0
Fork 0
mirror of https://github.com/Donchitos/Claude-Code-Game-Studios.git synced 2026-10-16 09:58:36 +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/settings/SKILL.md
+15 -7
View File
@@ -46,18 +46,26 @@ Anything else that doesn't match the four forms above → Phase 6 (usage).
## Phase 1: Load Helper
All four subcommands need `yaml-helper.sh`. Source it once via Bash:
All four subcommands need `yaml-helper.sh`. Each Bash call starts a fresh
shell, so load it **in the same command as every helper call**, from the project
root, in parentheses so the session's working directory does not change:
```bash
source "${CLAUDE_PROJECT_DIR:-.}/.claude/hooks/yaml-helper.sh"
(cd "${CLAUDE_SKILL_DIR}/../../.." && source .claude/hooks/yaml-helper.sh && <helper call>)
```
`<helper call>` is the function each phase below names, for example
`resolve_setting modes.review_mode` or `validate_yaml_enum project.yaml`.
Running from the root is what makes those `project.yaml` and
`project.local.yaml` arguments resolve when the session was started in a
subfolder.
If `.claude/hooks/yaml-helper.sh` is missing, this is not a CCGS project.
Report the error and exit.
## Phase 1b: Reserved-setting detection
Some settings are fully documented, enum-validated and settable, and **no skill
Some settings are fully documented and settable, and **no skill
or hook reads them** — setting one changes nothing. **This skill must say so.**
Returning an ordinary success lets a user reasonably believe the behaviour the
setting describes is now enforced — an accessibility tier being the case that
@@ -156,7 +164,7 @@ legitimate; storing it *silently* is the defect.
print this line with the legend below the block:
```
reserved = stored and validated, but nothing reads it. Setting it changes
reserved = stored, but nothing reads it. Setting it changes
no behaviour today.
```
@@ -185,7 +193,7 @@ Schema validation: ok
Effective config:
framework:
version: 1.1.2 (project.yaml, locked)
version: 1.1.3 (project.yaml, locked)
modes:
review_mode: lean (project.yaml)
@@ -241,8 +249,8 @@ Schema validation: ERRORS
**If `<key>` is in `RESERVED_SET`, print this BEFORE the value block** — above,
not below. A caveat under a value reads as a footnote on a working setting:
> **`<key>` is RESERVED — nothing reads it.** The value below is stored and
> validated; it changes no behaviour today.
> **`<key>` is RESERVED — nothing reads it.** The value below is stored; it
> changes no behaviour today.
Let `<key>` be the argument. Perform four reads: