PR-preflight — hygiene gates (read-only, no fixes)

This skill only judges — it never edits, stages, or fixes. Anything red is handed back to the caller (usually /execute-plans or /go), which decides what to do; the Scope line is consumed by the pr skill for branch/commit naming. Keeping it read-only is what makes it safe to run anywhere, anytime.

git status --short && git branch --show-current
git diff --name-only HEAD; git ls-files --others --exclude-standard

The gates

1. Dirty-tree coherence — modified + untracked files must tell ONE story. Clearly unrelated areas mixed together (backend + frontend + CI with no shared narrative) → blocker: "scope down before committing". A PR should have one story.
2. Branch safety — on main/master: REMEDIABLE finding (never commit to main; the pr skill is allowed to fix this one by creating the branch). On release-please-*: hard blocker — release automation owns that branch.
3. Secrets scan — any changed or untracked path matching .env*, *.pem, *.key, *.pfx, *credentials*, *secret*, daemon.token, *.keystore → hard blocker — except already-tracked *.example/*.sample files (e.g. .env.example), which are documentation, not secrets. Don't rationalize any other match; surface it.
4. `gh auth status` — fails → blocker (push/PR would die later anyway; fail fast here).
5. Scope detection — learn the repo's actual commit vocabulary (git log --oneline -30) and classify the change's dominant scope. Output it for the pr skill to reuse in branch and commit naming — don't invent scopes the repo never used.
6. Documentation sync — if .claude/rules/documentation-sync.md exists, check its trigger table against the changed paths; paired docs missing from the diff → flag (usually a real gap, not noise).
7. Pre-commit hooks installed? — test -f "$(git rev-parse --git-path hooks)/pre-commit" || git config core.hooksPath (worktree-safe — in a worktree .git is a file, so a literal .git/hooks check always misses); missing → one-line note, not a blocker (CI still catches it).

Output

PREFLIGHT — <PASS | BLOCKED | REMEDIABLE>
<gate>: <ok | BLOCKER: why | REMEDIABLE: why | note>
Scope: <type>(<scope>) candidates from repo vocabulary

Order findings by severity; one line each. Hard blockers stop the caller; the on-main REMEDIABLE finding is fixed by the pr skill (branch creation); notes are informational.