pr-preflightlisted

# PR Preflight (`/preflight`) Output "Read PR Preflight skill." to chat to acknowledge you read this file. Run this before every PR open or update. The goal is a review where the automated reviewer finds nothing, because you found it first. This skill is diff-aware: it knows what changed, audits those files completely (not just the diff lines), and looks for the same classes of issue that iterative review tools catch one-at-a-time. --- ## When to invoke - Before `gh pr create` or before pushing a PR update - When asked to "preflight", "pre-PR check", "prep for review" - After fixing review comments, before re-requesting review --- ## Phase 1 — Understand the Change Before anything else, map what this PR actually touches. ```bash # What branch and base? git branch --show-current git log --oneline main..HEAD 2>/dev/null || git log --oneline HEAD~5..HEAD # What files changed? git diff --name-only main..HEAD 2>/dev/null || git diff --name-only HEAD~1..HEAD # Full diff (for context) git diff main..HEAD 2>/dev/null || git diff HEAD~1..HEAD ``` From this, answer: - What is this PR trying to do? (1 sentence) - Which files were added, modified, deleted? - Which files were NOT changed but may be affected? (imports, callers, tests) **Do not skip this step.** Every later phase uses this map. --- ## Phase 2 — Stack Detection and Tool Audit Detect what's present and run the right tools. Do not run tools for stacks that aren't here. ```bash # Detect stack ls package.json t