Bug Report

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 Report" for me. It is the Game Studios structured bug-report skill, with four modes from its argument: a plain description becomes a structured report (title, allocated BUG-[NNNN] id, severity S1-S4 and priority P1-P4 on the same ladders /bug-triage parses, classification, environment, reproduction steps, technical context and evidence); analyze [path] reads the target file and drafts one report per potential bug found; verify [BUG-ID] re-checks a reported fix, running the related test through the project's configured commands.test when one exists and otherwise asking the user whether they played the reproduction steps, and updates the bug file's status only after asking; close [BUG-ID] appends a closure record to a Verified Fixed bug, again only after asking. Reports are written to production/qa/bugs/ only on a yes, and vendor bugs stay drafts in the report's Notes: the skill never files anything in an external tracker. Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/bug-report/ 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-report/ 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 cf643bf40ba2bfd45d580ecb5dfadb186b779b1152ca650962418bbcb3c8d783 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 (10488 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 the automation mode by running the template's hooks/yaml-helper.sh, follows the template's .claude/docs/automation-modes.md and directory-structure documents, reads project.yaml for the commands.test line its verify mode runs through Bash, and shares its severity/priority ladders with the template's /bug-triage skill — 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 searches and reads my project's own code and bug files locally. - At use time it writes only after asking, and only in my own project: new reports under production/qa/bugs/, status updates and closure records in the bug files themselves. No account, key, payment or third-party service is named in the files I read, and the skill states it never files, opens or comments on an issue or pull request in a vendor's repository. - Do not draft or file any bug report, do not run any test, 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-report folder into the agent's skills directory, in a folder named exactly "bug-report", keeping its 1 files in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: bug-report), 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 mode through the template's yaml-helper hook and runs the project's configured test command when verifying a fix), and that inside the template it files bug reports under production/qa/bugs/ only after asking). 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.