layout-inspect
星标2
分支1
更新时间2026年7月30日 18:38
Query airport ground graph topology via LayoutInspector CLI tool
安装
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
文件资源管理器
2 个文件SKILL.md
readonly来源
下载
相关职业SOC
基于 SOC 职业分类
菜单
Query airport ground graph topology via LayoutInspector CLI tool
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Prepare a YAAT release from CHANGELOG.md: verify release secret presence, choose version, draft highlights, promote the changelog heading, commit, tag, and push after approval.
End-to-end release of the current session's work: changelog + commit, land onto `main` in both repos, push, then close the related GitHub issue(s). Trigger when the user says "ship it", "ship this", "ship the session", "land and push", "push and close the issue", or invokes /ship. Composes /changelog-and-commit → /merge-session-to-main → push → `gh issue close`. Invoking the skill IS the approval — it pushes to origin/main and closes issues without further prompts.
Inspect, extract, install, and validate YAAT v4 bug bundles. Use when a *.yaat-bug-report-bundle.zip or *-recording.zip path appears in conversation, when triaging a YAAT controller bug report or recording-driven complaint, when correlating in-game behavior with recorded snapshots / actions / logs, or when fetching GitHub issue attachments into tests/Yaat.Sim.Tests/TestData/. Start with `info` for an overview, then `history --callsign X` for per-aircraft chronology.
Investigate and iterate on YAAT's speech-to-text pipeline. Auto-fires when a *.yaat-speech-sample.zip path appears in the conversation OR when the user provides a raw / paraphrased ATC transcript with an intent phrase like "why doesn't this match", "should this work", "what canonical would this produce", or "how do I make X recognize this". Walks the pipeline (callsign extract → rule mapper → LLM fallback), identifies the gap, and closes the loop with a TDD-driven fix (test → rule → verbalizer regression check → full suite).
Dedupe recording .zip files in tests/Yaat.Sim.Tests/TestData via tools/Yaat.RecordingConsolidator and commit the cleanup. Internal maintenance — do not update CHANGELOG.md.
Land the current Claude session's worktree commits onto `main` in both X:/dev/yaat and X:/dev/yaat-server. Cherry-picks divergent commits, auto-resolves the usual CHANGELOG.md `## Unreleased` bullet conflicts, runs each repo's pre-commit hooks, and stops (never pushes). Use when the user says 'merge to main', 'land this session', 'merge session', or invokes /merge-session-to-main after finishing work in a yaat worktree (typically `X:\dev\yaat.wt\<branch>\`).
| name | layout-inspect |
| description | Query airport ground graph topology via LayoutInspector CLI tool |
Query the airport ground graph for debugging ground/taxi/exit bugs. Wraps tools/Yaat.LayoutInspector.
GeoJSON airport files come from:
--airport <FAA> (cached at %LOCALAPPDATA%/yaat/cache/airports/). Preferred — works in any worktree without sibling-repo dependencies.tests/Yaat.Sim.Tests/TestData/<icao>.geojson (committed subset for tests: oak, sfo, fll, fat, hwd, mer, rno, sjc). Pass these paths positionally when offline.When the user asks about airport topology, runway exits, taxiway routing, node connectivity, or ground graph issues, use LayoutInspector to answer.
In every command below <geojson> is either a positional path (e.g. tests/Yaat.Sim.Tests/TestData/oak.geojson) or --airport <FAA> (e.g. --airport OAK) which downloads and caches the layout under %LOCALAPPDATA%/yaat/cache/airports/. The two forms are mutually exclusive.
Find all exits from a runway:
timeout 30 dotnet run --project tools/Yaat.LayoutInspector -- <geojson> --exits <RWY> --json 2>&1 | tee .tmp/li-exits.log
Trace a multi-hop exit path from a node through a taxiway:
timeout 30 dotnet run --project tools/Yaat.LayoutInspector -- <geojson> --bfs <NodeID> <Taxiway> --json 2>&1 | tee .tmp/li-bfs.log
Resolve a full pathfinder route (preferred for taxi-bug investigation — matches what GroundCommandHandler.TryTaxi does at runtime):
timeout 30 dotnet run --project tools/Yaat.LayoutInspector -- <geojson> --pathfinder <NodeID> T1 T2 T3 --pf-dest-rwy 28R 2>&1 | tee .tmp/li-pf.log
Inspect a specific node's connectivity:
timeout 30 dotnet run --project tools/Yaat.LayoutInspector -- <geojson> --node <NodeID> --json 2>&1 | tee .tmp/li-node.log
Inspect multiple nodes in one invocation (--node is repeatable):
timeout 30 dotnet run --project tools/Yaat.LayoutInspector -- <geojson> --node 619 --node 621 --node 1220 --node 1222 --node 1224 2>&1 | tee .tmp/li-cluster.log
Inspect a node and everything within N graph hops (--node-depth):
timeout 30 dotnet run --project tools/Yaat.LayoutInspector -- <geojson> --node 621 --node-depth 1 2>&1 | tee .tmp/li-621-d1.log
# Useful for dumping a fillet cluster without listing every member id by hand.
Diagnose junction corners — fan/turn angle of every edge pair + the bridging taxiway (--node-angles):
timeout 30 dotnet run --project tools/Yaat.LayoutInspector -- <geojson> --fillet-mode none --node 349 --node-angles 2>&1 | tee .tmp/li-angles.log
# Per pair: fan=included angle (0=parallel, 180=straight-through), turn=deflection (180-fan; high=sharp/un-filletable),
# and the shortest alternate path avoiding the node — "bridge via [G]" means another taxiway already joins the pair,
# so a direct corner-chord between them is redundant. Pairs sorted tightest-turn-first. Run on --fillet-mode none for
# the clean raw fan; on --fillet-mode standard to see the split tangent-cut nodes.
Show all nodes on a taxiway:
timeout 30 dotnet run --project tools/Yaat.LayoutInspector -- <geojson> --taxiway <T> --json 2>&1 | tee .tmp/li-twy.log
Inspect runway centerline and hold-short nodes:
timeout 30 dotnet run --project tools/Yaat.LayoutInspector -- <geojson> --runway <RWY> --json 2>&1 | tee .tmp/li-rwy.log
Dump entire airport to JSON for grepping:
timeout 30 dotnet run --project tools/Yaat.LayoutInspector -- <geojson> --dump 2>&1 | tee .tmp/li-dump.json
Generate interactive HTML visualization:
timeout 30 dotnet run --project tools/Yaat.LayoutInspector -- <geojson> --html .tmp/airport.html 2>&1 | tee .tmp/li-html.log
Most list-valued flags are repeatable AND accept comma-separated values — --node 619 --node 621 and --node 619,621 are equivalent. Mix freely.
| Flag | Repeatable / CSV | Purpose |
|---|---|---|
--node N | yes / yes | Node detail with edges |
--node-depth N | no | Expand each --node to include neighbors within N graph hops |
--taxiway T | yes / yes | All nodes/edges on a taxiway |
--runway 28R | yes / yes | Centerline + hold-short nodes |
--exits 28R | yes / yes | BFS-discovered exits with angle/side/high-speed classification |
--bfs N T | no | BFS trace from node N through taxiway T to hold-short |
--walk-trace N T | no | Detailed walker trace (developer diagnostic) |
--pathfinder N T1 T2 ... | no (greedy) | Resolve explicit taxi route through taxiway sequence; prints the resolved segments and the route's hold-short points (node, target, reason, cleared) |
--pf-dest-rwy R | no | Destination runway hint for --pathfinder |
--pf-hold-shorts HS | yes / yes | Explicit hold-short targets for --pathfinder |
--pf-dest-parking P, --pf-dest-spot S, --pf-dest-node N | no | Pathfinder destinations |
--exit-query RWY TWY [SIDE] | yes | Repeated targeted exit-query diagnostic |
--intersection T1 T2 | no | Find taxiway intersection node |
--distance N1 N2 | no | Straight-line (great-circle) distance + bearing between two nodes (ft + nm + °true) |
--path-distance N1 N2 ... | no (greedy) / yes | Cumulative distance + per-leg bearing along a node sequence; per-leg uses the graph edge (arc-aware) where one exists, else great-circle. Also reports heading range + total absolute turn (large = tracks a curve, near-zero = beeline) |
--parking / --spots | flag | Show parking / spot positions |
--dump | flag | Full airport JSON |
--json | flag | JSON output mode |
--no-fillets | flag | Parse without fillet arcs |
--debug-fillets / --debug-exits | flag | Enable subsystem debug logging |
--validate | flag | Run graph validation checks |
--html <path> | no | Interactive HTML render (pan/zoom, URL-persisted view) |
--html-taxiway T / --html-runway R / --html-node N / --html-route N | yes / yes | Highlight overlays for --html |
--html-annotate NODE TEXT | yes | Add a labeled annotation at a node |
--ticks <csv> | no | Overlay TickRecorder CSV as animated path |
--tick-table / --tick-summary | flag | Text-table analysis of a TickRecorder CSV |
--tick-range LO-HI | no | Filter tick analysis to inclusive range |
--tick-ref ICAO/RWY | no | Reference runway for xte/hdgErr columns |
--tick-hold-shorts HS | yes / yes | Distance columns to named hold-shorts |
--tick-callsign CS | no | Filter tick CSV to one callsign |
--airport-code ICAO | no | Override airport code (rare) |
--navdata <dir> | no | Override NavData directory |
--json for machine-readable output when analyzing programmatically.--debug-fillets when investigating fillet arc issues.--exits 28R --json gives structured exit data.--node 619,621,1222) and repeated --node for long ones (cleaner shell history).--airport OAK (fetches and caches) or tests/Yaat.Sim.Tests/TestData/oak.geojson (committed test data).