agentleFS
vchelaruvchelaru/Gum/.claude/skills/gum-tool-logging/SKILL.md

gum-tool-logging

Skill659 starsChanged 2 months agoMITView on GitHub

Diagnostic logging in the Gum tool via Gum.Diagnostics.ToolLog. Triggers: adding logging to hunt a bug, ToolLog, tool.log, TextureDiagnostics, "add logs", reading a log the user reproduced into.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    All tool diagnostics go through Gum.Diagnostics.ToolLog (Tools/Gum.Presentation/Diagnostics/ToolLog.cs).

    line 8
  2. Very specific:

    Never log per frame. Logging in shared runtime code (GumCommon, RenderingLibrary, MonoGameGum, other runtimes) is temporary and comes out …

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Gum Tool Logging

All tool diagnostics go through Gum.Diagnostics.ToolLog (Tools/Gum.Presentation/Diagnostics/ToolLog.cs). Never add a second logger. Wireframe/TextureDiagnostics.cs is an example of a thin helper that builds on it.

Rules (from the user)

  • Debug builds only. Release writes nothing and allocates nothing.
  • One file per tool session, named by the time the app started, so history is kept. The user never clears or deletes a log; the agent reads the newest one.
  • The agent deletes logs older than a month when it reads logs. The tool does not prune them.
  • Logging grows over time: add stages and events whenever they make the picture clearer. Start lines with a searchable prefix (texture.drop) and rename prefixes freely.
  • Never log per frame. Logging in shared runtime code (GumCommon, RenderingLibrary, MonoGameGum, other runtimes) is temporary and comes out once the bug is found; tool-side logging stays.

Where the files are

%TEMP%\Gum\Logs\tool-yyyyMMdd-HHmmss.log, one per session (ToolLog.DefaultPath); read the newest. GUM_TOOL_LOG overrides the path. GumPreview has its own log (PreviewDebugLog, preview.log plus .previous) that shares DiagnosticLogFile; tests are in AlwaysOnDebugLogTests.

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.