agentleFS
Sign inStart free
ThiagoFdaSLopesThiagoFdaSLopes/game-dev-skills/skills/game-debug/SKILL.md

game-debug

Skill2 starsChanged 24 days agoMITView on GitHub

Find the root cause of a gameplay bug, crash, regression, desync or odd behaviour and apply the smallest correct fix with regression coverage. Use when the user reports a bug, pastes a log, stack trace or repro steps, or asks "why does X happen". Never fabricates a root cause - labels hypotheses when reproduction is impossible.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. AirMile/claude-config★ 0same name
    2. mewzicians/Skills-Folder★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read before starting: references/principles.md, references/project-profile.md and the project profile itself, references/question-format.md.

    line 11
  2. Distinctive:

    Reproduce: - run the repro if the environment allows (tests, headless mode, a scripted scene, a log replay).

    line 16
  3. Distinctive:

    Trace: - follow execution and data flow from the trigger: input -> state -> systems -> output.

    line 17
  4. Distinctive:

    Cover: - add a regression test or a deterministic repro (unit, integration, play-mode, or a recorded input sequence) where the project …

    line 20
  5. Distinctive:

    Ask one shared-format question only when two fixes imply different behaviour the user must choose (e.g.

    line 29
  6. Distinctive:

    ask the user for facts in the logs or the repo

    line 44

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

game-debug

Reproduce, trace, isolate, fix at the smallest valid layer, prove it stays fixed.

Read before starting: references/principles.md, references/project-profile.md and the project profile itself, references/question-format.md. A fix follows profile: Workflow like any implementation; the checks to rerun are in profile: Checks.

Process

  1. Symptom - restate in one line what happens, what was expected, and the trigger. Pull engine version, platform and build config from the repo, not from the user.
  2. Reproduce - run the repro if the environment allows (tests, headless mode, a scripted scene, a log replay). If it cannot be reproduced here, say so and continue with a labelled hypothesis.
  3. Trace - follow execution and data flow from the trigger: input -> state -> systems -> output. Watch for the usual game suspects: frame-rate-dependent logic, order of update/fixed-update/physics ticks, event double-subscription, stale references across scene loads, serialization drift, float accumulation, authority mismatch in netcode.
  4. Isolate - name the root cause with its evidence label. Distinguish cause from where it shows up.
  5. Fix - the smallest change at the layer that owns the bug. Do not patch the symptom downstream.
  6. Cover - add a regression test or a deterministic repro (unit, integration, play-mode, or a recorded input sequence) where the project supports it.
  7. Verify - rerun the repro and the relevant tests. Report actual output.

When reproduction is impossible

Give, in this order: the most likely cause (inferred), one or two alternatives, and the cheapest diagnostic for each (a log line, an assertion, a debug overlay, a bisect). Do not pick a cause and pretend it was confirmed.

Fork

Ask one shared-format question only when two fixes imply different behaviour the user must choose (e.g. "clamp velocity" vs "reject the input"), or when the right behaviour is a pending item no recorded decision settles. Otherwise fix and note the alternative in Open risks.

Closing

Root cause:    one line + evidence label + file:line
Fix:           files changed, what the change does
Verification:  repro result before/after, tests run and their output
Open risks:    related code paths not covered, hypotheses still open

Never

  • invent a root cause or a passing test
  • fix three things while hunting one
  • ask the user for facts in the logs or the repo

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free