Audience

Repository maintainers, platform engineers, and technical leads preparing ProofKit for repeatable use.

1. Choose an installation path

Python-native path

Recommended when the team already uses Python tooling:

uv tool install proofkit-cli

or

pipx install proofkit-cli

Node wrapper path

Recommended when onboarding developers through npm:

npm install -g proofkit

2. Validate repository readiness

Run the full release gate locally before rollout:

python3 scripts/release_check.py

This validates packaging, tests, installed CLI smoke checks, workflow behavior, and published-artifact assumptions.

3. Enable local enforcement

Install hooks in target repositories:

proofkit install-hooks --root .

Hooks help prevent commits that bypass required repository governance.

4. Add CI enforcement