Test Flakiness

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 "Test Flakiness" for me. 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. The skill itself finds flaky tests from CI logs: it reads test-result history stored locally in the project (JUnit XML from GdUnit4 under reports/, NUnit XML from Unity under test-results/, Unreal automation logs under Saved/Logs/, or a log file path given as argument; it locates them with local ls commands), aggregates pass/fail outcomes per test across runs, and flags a test as flaky only when it both passed and failed with no code change in between (over 25% failures: quarantine immediately; 5-25%: investigate and fix soon; 1-5%: monitor; with fewer than 3 runs every finding is only 'suspected', whatever the rate). It classifies likely causes (timing/async, order dependency, random seed, resource leak, external state, floating point, scene load race) by grepping the test files, recommends the engine's own skip mechanism where the template's engine references document one (for gdUnit4 C# and Unreal it states the mechanism is NOT SOURCEABLE in the template's docs and asks the user instead of inventing one), and asks separately before updating the quarantine section of tests/regression-suite.md (it only ever adds entries, never removes any) and before writing the optional production/qa/flakiness-report-[date].md. It never deletes test files. It reads local logs only: it connects to no CI service and makes no network call. Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/test-flakiness/ 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/test-flakiness/ 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 382ee117ffbcade9c0b598db075a43087762da6873c5e7c7af67b0472e1d42b3 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. Nothing in the folder is a program; it is instructions the agent follows at use time. - 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 analysed 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 (a template file outside this skill's folder, absent standalone) and lists local result folders with ls. Inside the template it reads my project's CI logs and test-result XML locally; it connects to no CI service and makes no network call. - At use time it writes only after asking, twice and separately: appending new entries to the quarantine section of tests/regression-suite.md (never removing existing entries, never deleting test files), and the optional full report at production/qa/flakiness-report-[date].md. With fewer than 3 runs of data, its findings are labelled suspected, not confirmed. - Do not analyse any logs, 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 test-flakiness folder into the agent's skills directory, in a folder named exactly "test-flakiness", keeping its 1 files in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: test-flakiness), 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, and what it does inside the template). 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.