I kept hitting the same three cleanup problems on a project that had been through a few art passes and refactors, so I built a dock for each. All free, GDScript only, no dependencies.
Todo Tracker — walks every .gd/.cs/.shader/.gdshader file for TODO, FIXME, HACK, BUG, NOTE, plus any custom tag you type in (handy if your team writes REVIEW(name): or PERF:). Per-tag filter checkboxes, double-click a row to jump to the line, re-scans on save, and an “Export Markdown” button for pasting a checklist into a PR.
Broken Reference Finder — checks res:// paths in scenes, resources and scripts against files that no longer exist. The part that actually took the work: Godot scenes carry a uid="uid://..." next to the path, and Godot resolves by uid first, silently repairing a stale path on load. A plain text search flags that as broken when it isn’t. This one checks the uid against ResourceUID before reporting anything, and splits results into High/Low confidence (a preload() sitting inside a comment is Low, for example).
Unused Resource Finder — same uid-aware logic applied to “is this file referenced anywhere,” plus three checks that aren’t just orphan-hunting: oversized textures (>2048px on a side regardless of use), folders where every asset is unused, and asset folders with no LICENSE/CREDITS/ATTRIBUTION file nearby (the last one’s saved me a review hold-up more than once). Forum’s new-account link limit means I can’t drop a third URL in here — it’s on the same store page as the two above, same author.
All three are Godot 4.x, free, and open to feedback — especially if you’ve got a project layout that trips up the “unused” or “broken” detection, since static analysis like this always has edge cases I’d rather know about than guess at.
Following up on the uid:// part since a couple of people have asked me directly how that actually works under the hood (and it’s the part I’m most confident holds up under adversarial testing):
For every path="res://..." found in a .tscn/.tres, the scanner also looks for a sibling uid="uid://..." attribute on the same ext_resource line. If one is present, the path string is ignored entirely and the uid is resolved instead, with three calls:
var id := ResourceUID.text_to_id(uid_string)
if id == ResourceUID.INVALID_ID or not ResourceUID.has_id(id):
# genuinely broken - report it
var resolved_path := ResourceUID.get_id_path(id)
# resolved_path exists on disk -> not broken, even though the path string is stale
That’s the whole trick: Godot keeps its own uid → current-path table (ResourceUID) and repairs stale path= strings against it silently on load, so a plain text/regex search that only checks whether the literal path string exists on disk will flag a file as “broken” when Godot would have loaded it fine. This only kicks in for .tscn/.tres files touched since Godot 4.4 started writing uid= next to path= — older files or hand-edited ones without a uid still get the plain existence check.
For .gd/.cs files there’s no uid to fall back on, so those get a confidence tier instead of a binary broken/not-broken: a preload()/load() call matched inside a #/// comment, or immediately followed by %/+/.format( (i.e. it’s building a path at runtime, not a literal), gets marked Low rather than dropped silently - so you still see it, but you know to glance at it rather than trust it blindly.
Happy to dig into edge cases if anyone’s project trips either one up - that’s exactly the kind of thing I’d rather fix than have someone quietly distrust the tool.