Bug Triage

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — INTEGRATED SYSTEM FIRST: this skill is one piece of the complete "Claude Code Game Studios" template (49 agents, 74 skills, studio templates and a studio CLAUDE.md, per the repository README). Each skill assumes that template is installed, with its conventions, its project.yaml / project.local.yaml configuration, its .claude/docs/ mode documents, its hooks (for example hooks/yaml-helper.sh, outside this skill's folder) and its .claude/scripts/ helpers. Installing this listing alone copies only this skill's folder, without the rest of the system: the skill may reference template agents, files, hooks or scripts that are absent outside the full template, and it may not run as designed on its own. No account, no key and no payment are needed to copy the files, and nothing is run during installation. Install "Bug Triage" for me. It is the Game Studios bug-backlog triage skill. In sprint mode it assigns fixable open bugs to the current sprint (or flags priority overflow instead of overfilling it), in full mode it triages everything regardless of sprint scope, and in trend mode it produces a read-only trend report from the bug header fields alone, without reading full bug bodies. It loads the bug files under production/qa/bugs/, the current sprint plan when one exists, classifies each bug on the severity (S1-S4) and priority (P1-P4) ladders it shares with /bug-report, flags systemic patterns (3+ bugs in one system, regressions against completed stories), computes volume, hot-spot and age trends, presents the report and writes production/qa/bug-triage-[date].md only after approval. P4 candidates are surfaced and asked about, never decided on its own. Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/bug-triage/ folder at the pinned commit: 1 files in total) Pinned version: install the code at commit 05ad7c8a5b8aa2aa86bbd3439ae7cf7295cac418 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/Donchitos/Claude-Code-Game-Studios into a temporary folder, check out commit 05ad7c8a5b8aa2aa86bbd3439ae7cf7295cac418, and copy the .claude/skills/bug-triage/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 818f27203a1adfe2f5a6bc3a351a2673d5297d2fd3e69d773c228c98c8a83b01 If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 1 file only: SKILL.md (9375 characters of instructions in a single file; there are no companion files in its folder). Nothing in the folder is run during installation; companion files are instructions/references the skill reads at use time, copied as-is. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit, and no project of mine is read or modified. - Integrated-system reality, from the files: at use time the skill resolves studio configuration by running the template's hooks/yaml-helper.sh (keys automation, workflow), follows the template's .claude/docs/automation-modes.md, reads the severity reference in .claude/docs/coding-standards.md when it exists, and reads my project's sprint plans under production/sprints/ — files and conventions that live outside this skill's folder and are absent in a standalone install, so parts of it cannot run outside the full template. Inside the template it reads my project's own bug files locally. - At use time its only write is the triage report at production/qa/bug-triage-[date].md in my own project, and only after approval; the trend mode writes nothing. No account, key, payment or third-party service is named in the files I read. - Do not triage any backlog, do not run any template hook, and do not use the skill in any way during this install: using it is a separate step that only starts when I ask for it later. 3. When I say "yes, install", install it as a skill: copy the whole bug-triage folder into the agent's skills directory, in a folder named exactly "bug-triage", keeping its 1 files in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: bug-triage), the 1 files in place with matching fingerprints. Do not run anything from the folder and do not use the skill to verify. 5. Report what was installed, where, and what I still need to do myself (for example: that it belongs to the full Claude Code Game Studios template and may not run standalone (it resolves its settings through the template's yaml-helper hook and reads the template's docs), and that inside the template it triages my open bugs locally and writes its report only after approval). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.