What problem does it solve? Cutting a Python package release involves several consistency checks that are easy to skip or eyeball incorrectly: do all version declarations agree, does the proposed tag match the version, does a changelog section exist, and does the semver bump match the declared change class? This Skill runs those checks deterministically and reports uncertain for anything only a human can judge, instead of guessing. ## Core Features & Use Cases - Version-source discovery and agreement: Reads pyproject.toml ([project] and [tool.poetry]), package __init__.py __version__, the VERSION file, and .release-please-manifest.json, treating all sources as peers and failing on any disagreement. - Mechanical and judgment checks: Verifies tag/version consistency, changelog presence, and repo-supplied build/test gates mechanically, while change classification, version movement, and data-only track routing stay uncertain until a human supplies --change-class. - Authority deferral: When a repo carries a well-formed .domi-pin, the checker returns mode: defer and routes to DomI's release-integrity checker instead of running its own checks. - Use Case: Before tagging v1.6.0 and pushing to PyPI, ask whether the version declarations, proposed tag, and changelog are internally consistent, and get a per-check verdict list with a ready flag that never counts as publish authorization. ## Quick Start Ask the assistant to check whether the release in this repository is internally consistent for the proposed tag, supplying the previous version and change class if known.
