Skip to content

RandallLiuXin/GodotMaker / skills/reviewer/tilemap

tilemap-review

Verified

Reviews Godot TileMap implementation for known pitfalls. Triggers AFTER implementation, when code involves TileMapLayer, TileSet, TileSetAtlasSource, TileSetScenesCollectionSource, terrain painting, set_cell, erase_cell, get_cell_tile_data, collision polygons on tiles, or NavigationRegion2D with tile-based navigation. Do NOT use this skill for planning or teaching — only for post-implementation review.

FileKindSize
SKILL.mdskill md1.3 KB
checklist.mdmarkdown2.5 KB
gotchas.mdmarkdown3.8 KB
---
name: tilemap-review
description: |
  Reviews Godot TileMap implementation for known pitfalls.
  Triggers AFTER implementation, when code involves TileMapLayer, TileSet,
  TileSetAtlasSource, TileSetScenesCollectionSource, terrain painting,
  set_cell, erase_cell, get_cell_tile_data, collision polygons on tiles,
  or NavigationRegion2D with tile-based navigation.
  Do NOT use this skill for planning or teaching — only for post-implementation review.
---

# TileMap Review

Post-implementation reviewer for Godot TileMap code. Checks against known gotchas that LLMs consistently get wrong.

## When to trigger

After TileMap-related code is written or modified. Look for:
- TileMapLayer, TileSet, TileSetAtlasSource, TileSetScenesCollectionSource nodes
- Cell operations (`set_cell`, `erase_cell`, `set_cells_terrain_connect`)
- TileData access (`get_cell_tile_data`)
- Collision/navigation polygon configuration on tiles
- `y_sort_enabled` on TileMapLayer
- NavigationRegion2D with TileMapLayer children

## Review process

1. Read `gotchas.md`
2. Scan the implemented code against each gotcha
3. For each hit:
   - Cite the gotcha ID (e.g. G1)
   - Show the offending code
   - Provide the fix
4. If no hits, report clean
5. Optionally run `checklist.md` static checks for automated verification

When you need specific API details, delegate to the **godot-api** skill.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall