agentleFS
utopia-riseutopia-rise/godot-kotlin-jvm/.claude/skills/run-editor-probes/SKILL.md

run-editor-probes

Skill1k starsChanged 10 days agoMITView on GitHub

Run the editor-monkey probes that drive the real Godot editor (project generation, jar reloading, renames, Build on Run), or add a probe for a new editor feature. Use to test editor integration instead of clicking through the editor by hand.

Trending

Quiet since March.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the utopia-rise/godot-kotlin-jvm repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about utopia-rise/godot-kotlin-jvm

The biggest 5 of 49 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 49

Talked about on GitHub and Bluesky (49 times).

On GitHub · 48

43 more on GitHub

The file

Files
SKILL.md

Editor probes

harness/editor-monkey/ holds GDScript probes that start the official editor with -e -s, act like a user and assert on what the editor shows. harness/editor-monkey/README.md is the reference.

Run

  1. Build the host editor target of the native library (build-native skill); the probes copy it from harness/tests.
  2. From harness/editor-monkey/:
    ./run.sh --editor <path-to-godot-editor> [probe...]      # run.bat on Windows
    Without --editor, GODOT_EDITOR must be absolute. With no probe named, all run.
  3. Each probe writes <probe>.log. A run fails on a [MONKEY] FAIL line, a missing [MONKEY] DONE, a script error or a JVM exception. Godot-JVM error lines some scenarios produce on purpose are printed for inspection, not failures.

The first build inside a probe compiles the libraries and takes minutes; later ones take seconds.

Add a probe

Write probes/<name>.gd extending probes/common.gd: fill phases with [title, action, task] entries, where task is a toolbar entry such as "Build" or "", and assert in report(title) with expect(condition, description) and the helpers common.gd provides. Keep one scenario per probe, add it to the default list in run.sh and run.bat, and document it in the README's probe list.

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.