pre-pushlisted

> **ARCHIVED. Out of date, do not use.** > > This skill no longer loads: it lives in `archive/`, not `skills/`. Its stack > detection is stale, and the work it gated is now covered by `/factory` (which > adversarially reviews every diff before merge) and `/remediate` (which owns the > test-verified fix loop). See [the archive README](../README.md) for the why. > > Everything below this line is the original skill, kept for reference. --- # Pre-Push Everything you run before pushing to main, once you like the result. Each stage is a **gate**: it passes quietly, or trips on a genuine failure and stops for a fix. Never pushes — stops at the commit and hands back. ## Setup - Resolve the **target repo** root: `git rev-parse --show-toplevel`. Fails → not a git repo, stop. Run every stage from this path. - `git -C <root> status --short` empty → nothing to ship, stop. - Polish-and-ship, not build. Don't change behavior or add features. ## Detect the stack - **Node**: `package.json` exists. - **Python**: any of `pyproject.toml`, `setup.py`, `setup.cfg`, `requirements*.txt`, `Pipfile`, `tox.ini`. Both can be true — run both toolchains. Neither → skip stack commands, ask the user. Concrete commands per stack: [`stacks.md`](stacks.md). ## Gate: fixing what surfaces A gate trips only on a **genuine failure** — a security defect, a failing test, a functional bug — never a style nit or theoretical note. 1. Show the user the problem, location, and error/repro. Ask: `diagnosing-bugs