navigation-review

Review Godot navigation code against known pitfalls and recommend fixes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Prevents broken or misleading Godot navigation behavior by identifying common implementation pitfalls after navigation code is written, so agents don’t fail silently at runtime.

Core Features & Use Cases

  • Gotcha-based post-implementation review: Checks navigation code against a known set of stable Godot 4.x pitfalls for agents, regions, links, obstacles, and key APIs.
  • Actionable fixes with evidence: For each detected issue, it cites the gotcha ID, highlights the offending code, and recommends the correction pattern.
  • Automated/static and runtime verification guidance: Optionally uses the checklist and provides concrete tests to validate path sync, arrival correctness, rebake behavior, and multi-size/navmesh setup.
  • Use Case: When a new enemy/character navigation controller is added (e.g., NavigationAgent3D with target_position updates and avoidance), this skill helps ensure it won’t get stuck, query too early, snap to off-navmesh targets, or fail to re-path after rebakes.

Quick Start

Run the navigation-review after you implement or modify navigation-related code, then compare it against gotchas.md and confirm with the checklist checks in checklist.md.

Frequently Asked Questions about navigation-review

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

FAQPage Schema
Why does my Godot NavigationAgent get stuck or fail to pathfind at runtime?

Godot NavigationAgent pathfinding failures often stem from common gotchas like missing physics-frame sync, querying the navmesh before bake completion, or invalid target_position assignments. Post-implementation code review detects these issues by matching patterns to known pitfalls and recommending required fixes.

How do I review Godot navigation code for common implementation pitfalls?

Review Godot navigation code by checking implementations against stable 4.x gotchas for NavigationAgent2D/3D, NavigationRegion2D/3D, and obstacles. Match code patterns to gotcha IDs, highlight offending snippets, and apply correction patterns like stuck detection and off-navmesh distance validation.

What's the best way to handle navmesh rebake and repath behavior in Godot 4?

Navmesh rebake and repath behavior requires validating bake_navigation_polygon completion before re-pathing. Code review identifies missing rebake-then-repath sequences, ensuring agents don't query stale navigation data or fail silently after region updates.

Can I use this navigation review for both 2D and 3D Godot navigation?

Yes, the review covers NavigationAgent2D/3D, NavigationRegion2D/3D, NavigationLink2D/3D, and NavigationObstacle2D/3D. It validates velocity_computed, safe_velocity, avoidance_enabled, and is_navigation_finished across both dimensions.

How does Godot navigation avoidance work with velocity_computed and safe_velocity?

Godot navigation avoidance requires avoidance_enabled and handling velocity_computed signals to apply safe_velocity. Code review verifies physics-frame sync and proper signal connections, preventing agents from ignoring avoidance results or jittering during movement.