This skill helps an agent decouple Godot 4.7 nodes. A child emits a typed signal upward, the parent connects to it, and groups let one call reach every enemy or checkpoint without holding references.
It includes patterns for emitting from a reusable pickup, one-shot and bound connections, call_group broadcasts and a headless test that a signal has exactly one connection. A gotcha list covers duplicate connections from lambdas, argument mismatches, global group names and the Godot 3 connect syntax.
What You Get
- A core workflow from choosing the signal direction to connecting, using groups and checking the wiring at runtime
- GDScript patterns for emitting from a coin pickup, one-shot and bound connections, and call_group broadcasts
- A headless test that checks a signal has exactly one connection, plus a smoke run that greps the log for errors
- A gotcha list for duplicate lambda connections, lambdas that outlive their nodes, argument mismatches and groups shared across scenes
Common Use Cases
- Letting a pickup or enemy announce events without references to the HUD
- Debugging a handler that fires twice, never or logs already connected
- Pausing or saving every node in a group with one call
- Setting up an event bus autoload for cross-scene events
What Makes It Unique
The skill explains why a new lambda on every connect stacks silently and why call_group ignores nodes without the method, two causes of quiet bugs. It reads the connection lines in scene files, so an agent can wire editor connections as text, and it proves the result with a headless run.
Under The Hood
The agent loads the SKILL.md and, when needed, a reference on connection flags, awaiting signals and an event bus. It edits scene and script text files in your project, writes a small GDScript test, and runs the Godot binary headless, once for the test and once as a smoke run with output redirected to a log file that it searches with grep. If you edited scene connections it also runs the Python project checker from a sibling skill. It fetches no web pages and calls no APIs; without a Godot binary it asks you to run the command and paste the log.