Brightory
Brightory / AI Game Creation
GPT-6 Astra · Godot

How to Give GPT-6 Astra a Broken Godot Project Without Making the Codebase Worse

Freeze the broken state, identify the last known-good commit, collect the failing scene and logs, and ask for diagnosis before repair. Recover one broken contract at a time instead of letting the model “clean up” the entire Godot project.

7 min read · Updated Sep 5, 2026
Top-down game development workspace.
AI Game Creation · field notes
Direct answer

Freeze the broken state, identify the last known-good commit, collect the failing scene and logs, and ask for diagnosis before repair. Recover one broken contract at a time instead of letting the model “clean up” the entire Godot project.

Start with recovery information

A broken project needs two snapshots: what you have now and the last version that behaved correctly. The diff between them is often more informative than the full repository. Add the scene that reproduces the issue, autoloads or resources it depends on, and the Godot error output.

Map scene-tree dependencies before script edits

Godot bugs are frequently integration bugs: a node path changed, a signal stopped connecting, an exported property lost a value, or an autoload contract drifted. Ask the model to check those relationships before assuming the GDScript algorithm is wrong.

Recover in dependency order

  1. Restore project boot and scene loading.
  2. Restore required node paths, signals, and resources.
  3. Restore the failing mechanic.
  4. Run neighboring mechanic checks.
  5. Only then consider cleanup or architecture work.

Do not accept a wholesale rewrite as a recovery plan

A rewrite can make a small broken edge disappear while discarding behavior you have not documented. If the project is truly beyond repair, first inventory the contracts you need to preserve and rebuild behind those contracts deliberately; do not let the emergency debugging session decide that silently.

Working template

LAST GOOD COMMIT: [...]
BROKEN COMMIT: [...]
FAILING SCENE: [...]
ERROR OUTPUT: [...]
EXPECTED CONTRACTS: [signals, node paths, resources, save shape]
FIRST TASK: diagnose the smallest broken contract; no cleanup or rewrite.
VERIFY: boot → scene load → failing mechanic → neighbor checks.

Source and verification note

This guide was checked against OpenAI / Playco case study and updated Sep 5, 2026. Product behavior can change; current primary documentation should take precedence over this guide.