Package your standards. Own your edits.
Home · Get started · Tutorial · Concepts · Provider Development · AI Agent Reference
Repolish lets a team publish their repository conventions as providers and apply them consistently across every project that opts in — without overwriting the local changes that developers own.
Run repolish --check in CI to catch drift. Run repolish apply to pull in
updates.
uv add repolish
Development
Dev tasks are declared in mise-tasks/; run any of them with mise run <task>.
repo
| Task | Description |
|---|---|
build |
build the package (requires VERSION env var) |
build-docs |
build the static documentation site |
check-coverage |
run repolish and internal coverage suites |
check-dprint |
check dprint-managed formatting |
ci-checks |
run all checks for CI |
clean-docs |
clean docs build artifacts |
cov-contexts |
record per-test coverage contexts for the whole suite into .coverage |
cov-redundant |
report tests whose product-code coverage is duplicated elsewhere (run cov-contexts first) |
cov-reporting |
coverage of repolish.reporting from tests/reporting alone |
cov-summaries |
coverage of repolish.summaries from tests/summaries alone |
dev-docs |
start the docs development server |
format |
run all formatters |
format-dprint |
format dprint-managed files |
format-python |
format python code |
install-devkit-providers |
install all example providers in editable mode |
publish |
publish the package to PyPI (requires VERSION, PYPI_TOKEN, IS_RELEASE env vars) |
regen-changelog |
regenerate the changelog with releez |
setup |
sync the uv env, install the uv-toolbox envs, refresh ty.toml |
start-releez |
release start with releez |
check-coverage
| Task | Description |
|---|---|
check-coverage:internal |
run internal tests with internal coverage |
check-coverage:repolish |
run repolish tests with repolish coverage |
python
| Task | Description |
|---|---|
python:check:complexity |
complexity gate (fails above 20 on the complexipy 8.x scale) |
python:check:ruff |
ruff lint and format check (tools-env 0.17.1) |
python:check:types |
type check repolish source and root tests |
python:check:types:internal |
type check internal tools tree with repolish venv ty |
workspace
| Task | Description |
|---|---|
workspace:repolish |
apply repolish (local provider via the uvtb repolish env) |
workspace:repolish:check |
verify the repo matches repolish output (fails on drift) |
1 maintainer
Metadata
1 maintainer
Release files for repolish 1.17.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| repolish-1.17.2.tar.gz | 276.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| repolish-1.17.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 647.2 kB
Release files / repolish-1.17.2.tar.gz
| Download URL | repolish-1.17.2.tar.gz |
|---|---|
| Size | 276.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
911dcbeee8c481b1c8428f1cd5ca4c9402a484475e7f02838fd14611dbb9c6fd
|
|
BLAKE2b-256 checksum How to use checksums |
d0b721de5c5ea0083498b42be62e6f06213131d5dd8b89fd98b8c3f7263862d2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.27 {"installer":{"name":"uv","version":"0.9.27","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / repolish-1.17.2-py3-none-any.whl
| Download URL | repolish-1.17.2-py3-none-any.whl |
|---|---|
| Size | 370.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cf203ea888fdb57bf7b384ca2bd3d0c7788435f38034b943549ac9a3ccf10155
|
|
BLAKE2b-256 checksum How to use checksums |
8c82fcc0c0b6131187f99c6d509ceaa7d4f41508a8a8c38e24c2bad954c833dc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.27 {"installer":{"name":"uv","version":"0.9.27","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for repolish 1.17.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
