| 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
- Read
gotchas.md
- Scan the implemented code against each gotcha
- For each hit:
- Cite the gotcha ID (e.g. G1)
- Show the offending code
- Provide the fix
- If no hits, report clean
- Optionally run
checklist.md static checks for automated verification
When you need specific API details, delegate to the godot-api skill.
