pushlisted

# Push Skill Atomic test-commit-push workflow. Catches failures before they reach the remote. ## Steps ### Step 1: Detect Project Type Determine which test suites apply: - **Go:** Check for `go.mod` (or `cli/go.mod`). If found, Go tests apply. - **Python:** Check for `requirements.txt`, `pyproject.toml`, or `setup.py`. If found, Python tests apply. - **Shell:** Check for modified `.sh` files. If found, shellcheck applies (if installed). ### Step 2: Run Tests Run ALL applicable test suites. Do NOT skip any. **Go projects:** ```bash cd cli && go vet ./... cd cli && go test ./... -count=1 -short ``` **Python projects:** ```bash python -m pytest --tb=short -q ``` **Shell scripts (if shellcheck available):** ```bash shellcheck <modified .sh files> ``` If ANY test fails: **STOP.** Fix the failures before continuing. Do not commit broken code. ### Step 3: Stage Changes ```bash git add <specific files> ``` Stage only the files relevant to the current work. Do NOT use `git add -A` unless the user explicitly requests it. Review untracked files and skip anything that looks like secrets, temp files, or build artifacts. ### Step 4: Write Commit Message Write a conventional commit message based on the diff: - Use conventional commit format: `type(scope): description` - Types: `feat`, `fix`, `refactor`, `docs`, `test`, `chore`, `style`, `perf` - Keep subject line under 72 characters - Focus on WHY, not WHAT ### Step 5: Commit ```bash git commit -m "<message>" ``` ### Ste