tilemap-review

Review Godot TileMap code against known engine gotchas and cite fixes.

511|44|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/RandallLiuXin/GodotMaker --skill tilemap-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tilemap-review
Source: https://github.com/RandallLiuXin/GodotMaker/tree/main/skills/reviewer/tilemap
Command: npx skills add https://github.com/RandallLiuXin/GodotMaker --skill tilemap-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Prevents broken Godot TileMap behavior by identifying common TileMap/TileSet/NAV pitfalls right after implementation, so you can fix collision, terrain, TileData, scene tiles, and navigation issues early.

Core Features & Use Cases

  • Gotcha-based post-implementation review: Scans TileMap-related code against a curated gotchas list (collision polygons, terrain painting order, TileData sharing, y-sort batching, physics config placement, scene tile erase cleanup, and navigation rebake).
  • Precise, actionable findings: For each match, cites the gotcha ID, highlights offending code, and explains the fix.
  • Optional automated static checks: Runs checklist-based verification and includes both static and runtime checks when requested, including a headless Godot compilation step.

Quick Start

Ask an AI agent to run the tilemap-review skill after you implement or modify TileMapLayer/TileSet code, then summarize any detected gotchas and proposed fixes.

Frequently Asked Questions about tilemap-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I catch Godot TileMap collision polygon and navigation gotchas after implementation?

To catch Godot TileMap collision polygon and navigation gotchas, run a post-implementation code review against a curated list of known engine issues. This review detects physics misconfiguration, stale navigation rebakes, and incorrect terrain transitions.

Why does my Godot TileMapLayer scene tile erase leave orphaned nodes or cause TileData leakage?

TileMapLayer scene tile erase bugs and TileData leakage occur because Godot shares TileData across cells by default. A targeted code review identifies these scene-tile cleanup leaks and explains fixes citing the specific engine gotcha ID.

How do I review TileSet terrain painting order and y-sort batching issues in Godot?

Review TileSet terrain painting order and y-sort batching issues by matching your modified code against known Godot gotcha conditions. This process highlights offending code causing incorrect terrain transitions and y-sort performance degradation with actionable fixes.

Can I run static checklist checks and headless Godot compilation for TileMap debugging?

You can run static checklist checks and a headless Godot compilation validation for TileMap debugging. This optional automated verification step catches physics config placement errors and stale NavigationRegion2D navigation rebake issues at runtime.

What is the best way to fix incorrect TileSet collisions and physics misconfiguration in Godot?

The best way to fix incorrect TileSet collisions and physics misconfiguration is a gotcha-based post-implementation review. It scans your TileMapLayer and TileSet code, cites the exact gotcha ID, highlights offending code, and provides the fix.

When should I not use automated TileMap code review for my gamedev debugging?

Automated TileMap code review focuses strictly on post-implementation gotcha detection for collision polygons, terrain transitions, and navigation rebake issues. It should not replace manual testing when diagnosing unrelated gameplay logic or rendering pipeline faults.