gabe-pushlisted

# Gabe Push — env-aware shipping workflow **Usage:** `/gabe-push [env-name] [--epic] [--reconfigure]` ## Gabe execution contract (E1–E7) This skill runs under the suite execution contract — E1 EVIDENCE · E2 RUN-BEFORE-✅ · E3 NO SILENT DOWNGRADE · E4 REUSE FIRST · E5 STATE SYNC · E6 MISSING ANCHOR = STOP · E7 REPORT WHERE — floors, not ceilings; a skill's own gate may be stricter, never looser. Full text: `../gabe-docs/references/execution-contract.md` (if that file is missing, E6 applies — STOP). ## What this does Env-aware shipping. One command pushes local work to the configured target env, or promotes what's already on a pre-prod env (e.g., `staging`) up to the next env (e.g., `main`/`production`). Config lives in `.kdbp/PUSH.md`; first run interviews for envs (production-only, staging-then-prod, or custom N-env), subsequent runs honor the config until `/gabe-push --reconfigure`. Every run detects remote branch drift and offers cleanup of the source branch after a successful push. ## Procedure 1. Treat any text after the invocation as `$ARGUMENTS`. 2. Read `references/push-spec.md` (in this skill directory) IN FULL before executing — it is the binding spec: PUSH.md setup, env resolution, drift detection, push/PR/CI logic, DEPLOYMENTS.md capture, bookkeeping auto-commit, and branch cleanup. If it is missing, E6 applies — STOP. 3. Summary of the spec's main flow: - **Step 1** — validate `gh` CLI + auth + git remote; read `.kdbp/PUSH.md` if present. - **Non-inter