preflight-checkslisted

# Preflight Checks ## Core Question Is the current repository state ready for the requested next Git action, and what blocks or warnings remain? ## When To Use Use this skill when: - the user asks whether work is ready before commit, push, PR, merge, or release - a skill needs a read-only readiness gate - the user wants suggested verification commands - the user asks for blockers and risks before acting ## When Not To Use Do not use this skill when: - executing commits, pushes, merges, or releases - fixing detected blockers - running destructive cleanup - publishing artifacts Route to: - commit execution routes to `atomic-commits` - branch push or sync routes to `branch-workflow` or `sync-branch` - secret issues route to `secret-scan` - release prep routes to `version-bump`, `release-notes`, `changelog-maintenance`, or `tag-release` ## Required Evidence Before action, inspect or establish: - status and staged/unstaged/untracked groups - changed file list and diff summary - test, build, lint, and CI configuration - secret-like paths or values in changed files - generated or large file indicators - version, changelog, and release-note requirements - target action requested by the user No-evidence rule: - Do not make strong claims without observed evidence. - State assumptions when proceeding under incomplete evidence. - Stop when missing evidence affects safety, correctness, user work, remote state, or irreversible action. ## Operating Contract You MAY: - insp