Menu
Multi-agent Zig review of the pathfinder module for coherency, cohesion, and standards adherence. Use when the user asks for pathfinder review, pathfinding module review, /pathfinder-review, or a module-wide pass on src/game/systems/pathfinding/.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | pathfinder-review |
| description | Multi-agent Zig review of the pathfinder module for coherency, cohesion, and standards adherence. Use when the user asks for pathfinder review, pathfinding module review, /pathfinder-review, or a module-wide pass on src/game/systems/pathfinding/. |
Orchestrate a multi-phase review of the pathfinder module. You (parent) spawn all subagents — children cannot nest. Do not edit code unless the user asks for fixes after the report.
Agents: zig-review-specialist (.grok/agents/).
Unit table: .grok/skills/zig-workflows/references/module-presets.md → pathfinder.
Before reviewing, read:
- docs/coding-standards.md
- docs/simulation-tiers-and-pipeline.md
- docs/architecture.md
Hot/frame paths must be allocation-free after init/reserve/warmup; no per-frame
string lookups, hash-map dispatch, broad dynamic dispatch, or formatted logging
on hot paths. Production APIs expose runtime concepts only.
Spawn one zig-review-specialist per preset unit (system, nav_graph,
caches, solve, nav_grid, types_and_memory, group_field_and_scratch,
facade_and_test_support, benchmarks).
subagent_type: zig-review-specialist
capability_mode: read-only
background: true
description: pathfinder review <unit>
Prompt template:
Review unit "<unit>" of the ZeroLight-Framework pathfinder module.
Files (read in full):
- <files from preset>
Context: <note from preset>
<standards preamble>
<lenses>
Return severity-ordered findings (critical → nit). Each finding: severity,
category (coherency|cohesion|standards|performance|correctness), file, line,
title, detail, suggestion. If clean on a lens, say so in the summary — do not pad.
Collect all results with get_command_or_subagent_output before Phase 2.
Three more zig-review-specialist spawns (background: true):
| Unit | Focus |
|---|---|
module-coherency | Cross-file invariants; request lifecycle system → solve/nav_graph/nav_grid/caches |
module-cohesion | File split, facade surface, boundary violations, dead/duplicated code |
standards-and-hotpath | Post-warmup alloc, hot-path logging, naming, co-located tests |
List all pathfinder + benchmark files from the preset in each prompt.
Either synthesize yourself or spawn one zig-review-specialist with the full
corpus. Output one Markdown report:
file:line, problem, concrete fixDo not invent findings beyond the corpus. Do not fix code unless asked.
ZeroLight-Framework (Zig 0.16, SDL3, SDL_GPU) specialist routing: design, implement, debug, PR/diff review, and multi-phase review passes. Use when the user asks for zig-design-specialist, zig-specialist, zig-debug-specialist, or zig-review-specialist; when zig build, zig test, or shader compile fails; when reviewing a PR or branch diff; when planning ECS, DataSystem, SimulationPipeline, pathfinding, collision, AI, or threading changes; or when assessing emergent-gameplay architecture readiness. Slash: /zig-workflows.
Assess ZeroLight-Framework architecture for scalable emergent gameplay simulation. Use when the user asks how ready the engine is for emergent gameplay, architecture assessment, extensibility review, or runs /architecture-assessment.
Multi-agent Zig best-practices review of large hot subsystems: review, adversarial verify, then synthesize durable lint/agent/doc guidance. Use when the user asks for best-practices review, Zig idioms pass, durable lint guidance, or /zig-best-practices-review.
Deep behavioral correctness review (pass 3): concurrency, algorithms, SIMD parity, pipeline determinism, resource lifetime, outliers, and test-coverage gaps. Use when the user asks for deep correctness, concurrency review, determinism audit, race hunting, or /zig-deep-correctness-review. Goes beyond idiom/surface reviews.
ZeroLight-Framework (Zig 0.16, SDL3, SDL_GPU) specialist workflows: design plans, implementation, debug/triage, PR/diff review, pathfinder module review, architecture assessment. Use when the user asks for zig-design-specialist, zig-specialist, zig-debug-specialist, or zig-review-specialist; when zig build, zig test, or shader compile fails; when reviewing a PR or branch diff; when planning ECS, DataSystem, SimulationPipeline, pathfinding, collision, AI, or threading changes; or when assessing emergent-gameplay architecture readiness.