ksh999000/Claude-Code-Game-Studios
1
0
Fork 0
mirror of https://github.com/Donchitos/Claude-Code-Game-Studios.git synced 2026-10-16 01:37:05 +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
.claude/skills/bug-triage/SKILL.md
+10 -6
View File
@@ -56,7 +56,7 @@ If no bug files found:
> different location, adjust the glob pattern. If no bugs exist yet, there is
> nothing to triage."
Stop and report. Do not proceed if no bugs exist.
Stop and report. Do not proceed if no bugs exist. Verdict: **COMPLETE** — no bug files in `production/qa/bugs/`; nothing to triage.
**In `trend` mode, do not read full bug bodies.** Trend metrics (volume, severity
mix, by-system, by-date) are computable from the header fields alone:
@@ -185,7 +185,7 @@ After classifying all bugs, generate trend metrics:
| ID | System | Severity | Summary | Assigned to | Story |
|----|--------|----------|---------|-------------|-------|
| BUG-NNN | [system] | S[1-4] | [one-line description] | [sprint] | [story path] |
| BUG-NNNN | [system] | S[1-4] | [one-line description] | [sprint] | [story path] |
---
@@ -193,7 +193,7 @@ After classifying all bugs, generate trend metrics:
| ID | System | Severity | Summary | Target Sprint |
|----|--------|----------|---------|---------------|
| BUG-NNN | [system] | S[1-4] | [one-line description] | Sprint [N+1] |
| BUG-NNNN | [system] | S[1-4] | [one-line description] | Sprint [N+1] |
---
@@ -201,7 +201,7 @@ After classifying all bugs, generate trend metrics:
| ID | System | Severity | Summary | Disposition |
|----|--------|----------|---------|-------------|
| BUG-NNN | [system] | S4 | [one-line description] | Backlog |
| BUG-NNNN | [system] | S4 | [one-line description] | Backlog |
---
@@ -235,7 +235,9 @@ After classifying all bugs, generate trend metrics:
## 6. Write and Gate
Present the report in conversation, then ask:
Present the report in conversation. If any bug is a P4 candidate, first ask
"Are these acceptable as Won't Fix?" and keep its disposition `P4 candidate`
until the user answers. Then ask:
"May I write this triage report to `production/qa/bug-triage-[date].md`?"
@@ -246,7 +248,9 @@ After writing:
can be considered healthy. Run `/sprint-status` to see current capacity."
- If regression bugs exist: "Regressions found — consider re-opening the
affected stories in sprint tracking and running `/smoke-check` to re-gate."
- If no P1 bugs exist: "No P1 bugs — build is in good shape for QA hand-off." Verdict: **COMPLETE** — triage report written.
- If no P1 bugs exist: "No P1 bugs — build is in good shape for QA hand-off."
Then, whether or not P1 bugs exist: Verdict: **COMPLETE** — triage report written.
If user declined write: Verdict: **BLOCKED** — user declined write.