pr-preflightlisted

# PR Preflight (`/preflight`) If running interactively (human present), output "Read PR Preflight skill." to acknowledge. If running with --dangerously-skip-permissions (AFK/unattended), skip acknowledgement and proceed directly. 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. **Resolve the base branch authoritatively** — never assume `main`. The PR's base may be `dev` (as in ctrlshft), and guessing wrong makes the diff meaningless. ```bash # Resolve the authoritative base (PR base → sandcastle.config.json → repo default) BASE_BRANCH="$(bash bin/verify-pr-base.sh --branch "$(git branch --show-current)")" # If the branch has an open PR, prefer its authoritative base: # BASE_BRANCH="$(bash bin/verify-pr-base.sh --pr <PR_NUMBER>)" # What branch and base? git branch --show-current git log --oneline "$BASE_BRANCH"..HEAD 2>/dev/null || git log --oneline HEAD~5..HEAD # What files changed? git diff --name