py-package-check

name	py-package-check
description	Run the Python package release gate for geobr — sync the locked environment, run the offline and network test suites, build the distribution, and review the source against the Python conventions. Use when the user says "check the python package", "run pytest", "is the python side ready", "prepare a PyPI release", or points at python-package/. Produces a check report in quality_reports/. Mirrors .github/workflows/Python-CMD-check.yaml so local and CI cannot diverge.
author	geobr
version	1.0.0
argument-hint	[--network] [--no-review]
disable-model-invocation	true
allowed-tools	["Read","Grep","Glob","Bash","Write","Task","Monitor"]
effort	high

/py-package-check — Python Release Gate

The Python counterpart to /r-package-check. Sync → test → build → review, then a verdict.

Input: $ARGUMENTS — --network also runs the online suite (hits geobr_prep_data); --no-review skips the agent review pass.

---

Constraints

• Mirror CI exactly. .github/workflows/Python-CMD-check.yaml is the source of truth for the commands. If they drift, CI wins and this file is updated.
• Follow python-package-conventions.md.
• Do not bump the version and do not publish. This skill checks; the maintainer releases.

---

Phase 0: Toolchain pre-flight — this is the gate on the gate

command -v uv || echo "uv: ABSENT"
command -v python || command -v python3 || echo "python: ABSENT"

If uv is absent (the expected case on the maintainer's Windows machine), stop here and report:

## Pre-Flight — HALTED

**Python toolchain:** not available on this machine (no `uv`, no `python`, no `.venv`).

This skill cannot run. Your options:
1. Push the branch and let `Python-CMD-check.yaml` run it (ubuntu/macOS/windows x py3.10-3.13).
2. Install uv — https://docs.astral.sh/uv/getting-started/installation/ — then re-run.
3. Run `/py-package-check --no-review` on a machine that has Python.

**Falling back to static review**, which needs no interpreter: [proceed to Phase 4].