Repository-local maintenance commands live under dev/cli.
Run the command group from the repo root with:
uv run python -m dev.cli --helpCommon commands:
uv run python -m dev.cli docs build
uv run python -m dev.cli docs dev
uv run python -m dev.cli docs publish 5.0.0 latest
uv run python -m dev.cli ai skill-ref
uv run python -m dev.cli build
uv run python -m dev.cli release-check
uv run python -m dev.cli publishNotes:
docs ...uses thedocsdependency group automatically.docs publish <version> <alias>publishes patch versions under their minor docs line. For example,5.0.0deploys as5.0.x, andlatestpoints to that docs line.buildrefreshes packaged AI skill references, rebuildsdist/, builds docs, runsuv build, then validates the built distributions.release-checkruns the local release gate: tests, lint, type check, docs build, package build, metadata validation, and install smoke tests.publishrunsbuildfirst, thenuv publish.
Before publishing:
-
Bump the version in
pyproject.tomlanduv.lock. -
Update
CHANGELOG.md. -
Run:
uv run python -m dev.cli release-check
-
Confirm PyPI credentials or trusted publishing are configured.
-
Publish:
uv run python -m dev.cli publish
Package versions and git tags stay exact, such as 5.0.0 and v5.0.0.
Published docs are grouped by minor release line, such as 5.0.x.
For a patch release, publish docs only when the docs changed or the patch changes documented behavior:
uv run python -m dev.cli docs publish 5.0.0 latestThe docs command deploys that example as 5.0.x and sets latest to the same docs line.