godot-add-signals

What problem does it solve?

Tight coupling in Godot projects often arises from direct get_node(), get_parent(), or runtime references, making code brittle and hard to test. This skill transforms such coupling into signal-based communication so components become independent, testable, and reusable.

Core Features & Use Cases

• Introduces typed signals for common events and replaces direct method calls with signal emissions.
• Provides orchestrator wiring to connect signals to listeners, enabling reusable components across scenes.
• Use case: refactor a player UI and gameplay logic to communicate via signals instead of direct scene navigation.

Quick Start

1. Enable this skill and scan your project for get_node/get_parent usage.
2. Define signals in relevant scripts, emit them at appropriate times, and connect listeners in the orchestrator.
3. Run automated validation with Git commits to preserve behavior.