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:48:34 +00:00
Code Issues Packages Projects Releases Wiki Activity

Release 1.1.2 — the default path works end to end

Browse Source 
Fix release for 1.1.1: the minimal path end to end, engine commands that
run on Godot, Unity and Unreal, hook warnings you can see, and verdicts
that say when they could not check. Details in CHANGELOG.md; upgrade
steps in UPGRADING.md (v1.1.1 → v1.1.2).

Fixes #67
Fixes #131

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WuJn2FdynEybfL5KC697nJ
This commit is contained in:
Donchitos
2026-09-29 21:32:19 +10:00
co-authored by Claude Opus 5.5
parent 7ed2c3e9c4
commit b21fa0f7f2
383 changed files with 22888 additions and 10618 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CCGS Skill Testing Framework/CLAUDE.md
+29 -16
View File
@@ -9,11 +9,11 @@ framework. It is self-contained and separate from any game project.
|------|---------|
| `catalog.yaml` | Master registry for all 74 skills and 49 agents. Contains category, spec path, and last-test tracking fields. Always read this first when running any test command. |
| `quality-rubric.md` | Category-specific pass/fail metrics. Read the matching `###` section for the skill's category when running `/skill-test category`. |
| `skills/[category]/[name].md` | Behavioral spec for a skill — 5 test cases + protocol compliance assertions. |
| `agents/[tier]/[name].md` | Behavioral spec for an agent — 5 test cases + protocol compliance assertions. |
| `skills/[category]/[name].md` | Behavioral spec for a skill — 5 or more test cases + protocol compliance assertions. |
| `agents/[tier]/[name].md` | Behavioral spec for an agent — 5 or more test cases + protocol compliance assertions. |
| `templates/skill-test-spec.md` | Template for writing new skill spec files. |
| `templates/agent-test-spec.md` | Template for writing new agent spec files. |
| `results/` | Written by `/skill-test spec` when results are saved. Gitignored. |
| `results/` | Written by `/skill-test spec` when results are saved. Not gitignored — add it to `.gitignore` to keep results out of commits. |
## Path conventions
@@ -67,13 +67,23 @@ operations → devops-engineer, release-manager, live-ops-designer,
qa → qa-tester, security-engineer, accessibility-specialist
```
## Workflow for testing a skill
A tier is the directory a spec lives in. The rubric category is the agent's
`category:` in `catalog.yaml` and can differ: `security-engineer` and
`accessibility-specialist` sit in `qa/` but are rated as `specialist`.
1. Read `catalog.yaml` to get the skill's `spec:` path and `category:`
2. Read the skill at `.claude/skills/[name]/SKILL.md`
3. Read the spec at the `spec:` path
4. Evaluate assertions case by case
5. Offer to write results to `results/` and update `catalog.yaml`
## Workflow for testing a skill or agent
1. Read `catalog.yaml` to get the `spec:` path and `category:` — from the
`skills:` entry for a skill, the `agents:` entry for an agent
2. Read the skill at `.claude/skills/[name]/SKILL.md`, or the agent at
`.claude/agents/[name].md`
3. Read the project `CLAUDE.md` and the files it imports with `@`: every
subagent receives them, so a rule stated there (for example a redirect in
`coordination-rules.md`) counts as the skill's or agent's own
4. Read the spec at the `spec:` path
5. Evaluate the spec's Static Assertions, each case's assertions, and its
Protocol Compliance list
6. Offer to write results to `results/` and update `catalog.yaml`
## Workflow for improving a skill
@@ -82,13 +92,16 @@ test → diagnose → propose fix → rewrite → retest → keep or revert.
## Spec validity note
Specs in this folder describe **current behavior**, not ideal behavior. They were
written by reading the skills, so they may encode bugs. When a skill misbehaves in
practice, correct the skill first, then update the spec to match the fixed behavior.
Treat spec failures as "this needs investigation," not "the skill is definitively wrong."
Specs in this folder assert the **correct** behavior, not whatever a skill or agent
does today. A failing assertion means the skill or agent is wrong until shown
otherwise: fix it and re-run, and never weaken an assertion just so it passes.
Specs can be wrong too — when one asserts behavior that is itself incorrect,
correct the spec toward the right behavior, not toward what the skill currently does.
## This folder is deletable
Nothing in `.claude/` imports from here. Deleting this folder has no effect on the
CCGS skills or agents themselves. `/skill-test` and `/skill-improve` will report that
`catalog.yaml` is missing and guide the user to initialize it.
Nothing in `.claude/` imports from here, and every other CCGS skill and agent works
without it — but `/skill-test` and `/skill-improve` read it by path. Without it,
`/skill-test static` still works, `/skill-test spec` and `/skill-test category`
stop working, `/skill-test audit` reports that no catalog exists, and
`/skill-improve` skips its category checks (the table in `README.md` has the detail).