godot-clean-conflicts

What problem does it solve?

Godot projects frequently suffer from conflicting operations between code and scene data, causing undefined behavior and hard-to-trace bugs. This Skill detects cross-domain conflicts and applies a clear ownership model so the game logic remains predictable and maintainable.

Core Features & Use Cases

• Detect Property Conflicts across _ready, _process, and editor data (.tscn/.tres)
• Detect Duplicate Signal Connections and animation/code ownership clashes
• Detect Physics/Movement conflicts between code and physics engine
• Detect Animation ownership conflicts when multiple systems modify properties
• Apply deterministic resolution strategies (Editor wins, Code wins, Animation wins, Physics wins)
• Generate changelog-like documentation and commit-ready diffs for traceability
• Works as part of full Godot refactor orchestrations

Quick Start

Use this skill on a Godot project to scan for cross-domain conflicts and apply ownership-based resolutions. After execution, review the generated comments and updated scenes, then run the project to validate behavior.