godot-ops

Automate MCP-based build-test-fix loops for Godot games.

8|3|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/HubDev-AI/godot-ai-builder --skill godot-ops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: godot-ops
Source: https://github.com/HubDev-AI/godot-ai-builder/tree/main/skills/godot-ops
Command: npx skills add https://github.com/HubDev-AI/godot-ai-builder --skill godot-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

MCP tool operations streamline the process of repeatedly building, running, and debugging Godot projects by providing a standardized, auditable workflow for testing and iteration.

Core Features & Use Cases

  • Execute deterministic build-test-fix loops using MCP tools: godot_reload_filesystem, godot_run_scene, godot_get_errors, etc.
  • Enforce progress visibility via mandatory dock logging, with status updates after every action.
  • Improve iteration efficiency during testing and debugging of Godot projects, from initial bootstrapping to error resolution.

Quick Start

Enable MCP tooling and initiate the build-test-fix loop to start running the project and addressing errors.

Frequently Asked Questions about godot-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate build and test loops for Godot game projects?

Automating Godot build and test loops involves using MCP tools like godot_run_scene and godot_get_errors to repeatedly run scenes, read errors, and apply fixes. This enforces a deterministic workflow with mandatory progress logging.

What is the MCP workflow for debugging Godot scenes?

The MCP workflow for debugging Godot scenes utilizes tools such as godot_reload_filesystem, godot_run_scene, and godot_get_errors to execute build-test-fix cycles. It provides continual progress visibility via the Godot dock.

Do I need specific MCP tools to run automated Godot testing?

Yes, running automated Godot testing requires access to specific MCP tools including godot_reload_filesystem, godot_run_scene, and godot_get_errors. These tools enable the standardized build-test-fix loop.

How can I track progress when running iterative Godot build cycles?

Tracking progress during iterative Godot build cycles is handled through mandatory dock logging, which provides status updates after every action. This ensures iteration efficiency and visibility during testing.

What's the best way to resolve errors during Godot game iteration?

Resolving errors during Godot game iteration is best achieved through an automated build-test-fix loop using MCP tools to read errors and reload the filesystem. This streamlines debugging from initial bootstrapping to resolution.