GDH

GDH helps AI coding agents work inside Godot projects without guessing the project shape, commands, runtime setup, or validation evidence.

Quick Start

Run this from the Godot project or repo you want GDH to manage:

npx -y @skillcap/gdh@latest setup

Then open your agent in that project and run:

/gdh-onboard

GDH writes the project guidance, agent skill surfaces, MCP config, and local state that supported agents use for future work. In monorepos, full guidance and skills stay in the selected Godot project directory while only thin root routing/config surfaces are installed for agents launched from the repo root. Setup records the resolved GDH version in the target project so later updates can migrate that project deliberately.

Requirements

• Node.js 20 or newer.
• A local Godot project, currently focused on Godot 4.4 through 4.6.
• A supported AI coding agent: Codex, Claude, or Cursor.
• Optional: GDH_GODOT_EDITOR_BIN for Godot import refresh or direct local runtime checks.
• Optional: Docker for the Docker-backed rendered runtime path.

What It Does

• Finds Godot project roots and writes .gdh/project.yaml plus .gdh-state/ derived state.
• Installs agent commands and skills such as /gdh-status, /gdh-prepare, /gdh-check, /gdh-migrate, and /gdh-update.
• Exposes MCP tools for project status, authoring checks, docs lookup, runtime bridge operations, and verification.
• Keeps generated target-project files inside the managed project, not in GDH's own implementation repo.

Common Commands

npx -y @skillcap/gdh@latest setup
gdh status
gdh target prepare --dry-run
gdh authoring check --mode final
gdh authoring check --mode post-edit --changed res://scripts/player.gd --format compact
gdh self-update --dry-run --target .

More Docs

• Install and update
• Advanced CLI usage
• Runtime support matrix
• Runtime release readiness
• All docs

License

MIT