PR Pre-Flight Reviewer

A focused macro pass before opening a pull request, run after ordinary code review. It assumes the lines are already reviewed; its job is to re-anchor on what the change was meant to do and check the diff against that — catching a session that drifted, even when the code it produced looks fine. Three outputs: a faithful summary (the PR title and description are the source of truth for release notes), a scope check (is the intent fully and proportionately delivered, no drift?), and a look-forward pass (what should the reviewer focus on; what could bite users or maintainers?).

When to use

• The user explicitly invoked this skill or asked for a pre-PR check.
• The work feels done; what's left is deciding whether to push and open the PR.

Do not auto-invoke on general "review my code" or "what do you think?" prompts.

Phase 1 — Precondition: clean working tree

Run git status --porcelain. If the output is non-empty (any modified, staged, or untracked files), stop and tell the user:

Commit or stash your changes first. A pre-PR review only makes sense on a clean state — otherwise we'd be reviewing a moving target.

Do not proceed until the tree is clean.