mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios.git
synced 2026-10-16 01:37:05 +00:00
Release 1.1.0 — one config file, and a process weight you choose
`project.yaml` at the repo root is now the single source of truth for a project's configuration, replacing `production/stage.txt`, `production/review-mode.txt` and `.claude/docs/technical-preferences.md` (all three still read as a fallback; nothing is force-deleted). **`modes.rigor` — one question instead of six.** `minimal`, `standard` or `full` fronts six knobs: `modes.workflow`, `docs.density`, `qa.level`, `modes.story_granularity`, `modes.review_mode` and `team.size`. It defaults to `minimal`, which is a change from 1.0's behaviour: the heavier tier was measured costing several times more to reach working code without producing a better result, and returning nothing when a fresh developer inherited the project. Pin `modes.rigor: standard` to keep 1.0's process level. Also in this release: - `/settings` to view or change any setting, and `project.local.yaml` for per-developer preferences that should not be committed. - `system_overrides` to hold one system to a higher standard than the rest of the project, and `testing.strict` to set per test type whether missing evidence blocks a story or warns. - A story that changes anything the player sees is not closed until the game has been launched, observed, and a screenshot retained in `production/qa/evidence/`. A parse check is not a run. This holds at every rigor level, including `minimal`, where automated tests are waived but the look is not. - The code root is engine-specific and enforced as such: Godot `src/`, Unity `Assets/`, Unreal `Source/<Module>/`. Two of the three will not build a project laid out any other way. - Migration tooling for existing projects: `.claude/scripts/migrate-v1-config.sh` converts a 1.0 layout, non-destructively by default, with a report to review before `--finalize` deletes anything. - Ask-before-write holds regardless of personal automation settings. Upgrading from 1.0 or earlier: see UPGRADING.md. Full list of changes: CHANGELOG.md. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016xvzG3i7pWQg4LjyDwWMXd
This commit is contained in:
co-authored by
Claude Opus 5
parent
984023ddac
commit
d05699707f
@@ -1,12 +1,20 @@
|
||||
---
|
||||
name: bug-report
|
||||
description: "Creates a structured bug report from a description, or analyzes code to identify potential bugs. Ensures every bug report has full reproduction steps, severity assessment, and context."
|
||||
description: "Structured bug report from a description, or analyze code for potential bugs. Reproduction steps, severity."
|
||||
argument-hint: "[description] | analyze [path-to-file]"
|
||||
user-invocable: true
|
||||
allowed-tools: Read, Glob, Grep, Write
|
||||
allowed-tools: Read, Glob, Grep, Bash, Write, Edit
|
||||
model: sonnet
|
||||
---
|
||||
|
||||
!`source "${CLAUDE_PROJECT_DIR:-.}/.claude/hooks/yaml-helper.sh" 2>/dev/null && resolve_config --keys automation`
|
||||
|
||||
**Automation mode**: Resolve `modes.automation` (`project.local.yaml` →
|
||||
`project.yaml` → default `collaborative`). Every `AskUserQuestion` call and
|
||||
every file write follows `.claude/docs/automation-modes.md`
|
||||
(collaborative asks always · guided major-only · autonomous logs and proceeds;
|
||||
`automation_always_ask` categories always prompt).
|
||||
|
||||
## Phase 1: Parse Arguments
|
||||
|
||||
Determine the mode from the argument:
|
||||
@@ -35,7 +43,14 @@ If no argument is provided, ask the user for a bug description before proceeding
|
||||
**Title**: [Concise, descriptive title]
|
||||
**ID**: BUG-[NNNN]
|
||||
**Severity**: [S1-Critical / S2-Major / S3-Minor / S4-Trivial]
|
||||
**Priority**: [P1-Immediate / P2-Next Sprint / P3-Backlog / P4-Wishlist]
|
||||
**Priority**: [P1-Fix this sprint / P2-Fix soon / P3-Backlog / P4-Won't fix]
|
||||
|
||||
> **These labels must match `/bug-triage`'s priority table exactly** — it parses
|
||||
> this field out of the file you are writing. P4 is the easiest to get wrong:
|
||||
> `P4-Wishlist` ("would be nice someday") and `P4 — Won't fix / Deferred`
|
||||
> ("accepted risk, not doing it") mean opposite things, and nothing at runtime
|
||||
> surfaces a disagreement between the producer and consumer of the field. If you change this ladder, change
|
||||
> `.claude/skills/bug-triage/SKILL.md` in the same commit.
|
||||
**Status**: Open
|
||||
**Reported**: [Date]
|
||||
**Reporter**: [Name]
|
||||
|
||||
Reference in New Issue
Block a user