Metadata-Version: 2.4
Name: repo-standards
Version: 6.23.1
Summary: Deterministic pull-request sizing and reviewed repository policy
Keywords: architecture,github-actions,lint,openapi,repository
Author: sarj-ai
License-Expression: MIT
License-File: LICENSE
Classifier: Development Status :: 4 - Beta
Classifier: Environment :: Console
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.14
Classifier: Programming Language :: Python :: 3.15
Classifier: Typing :: Typed
Requires-Dist: conventional-pre-commit==4.4.0
Requires-Dist: markdown-it-py==4.2.0
Requires-Dist: pyyaml>=6.0.3,<7
Requires-Dist: pydantic>=2.14.1,<3
Requires-Dist: typer>=0.27.3,<1
Requires-Python: >=3.14, <3.16
Project-URL: Homepage, https://engineering.sarj.ai/projects/repo-standards/
Project-URL: Repository, https://github.com/sarj-ai/repo-standards
Project-URL: Issues, https://github.com/sarj-ai/repo-standards/issues
Project-URL: Documentation, https://engineering.sarj.ai/projects/repo-standards/
Description-Content-Type: text/markdown

# repo-standards

`repo-standards` measures pull-request review size without executing repository code. Its
repository rules are available for review but remain disabled until individually approved
and explicitly activated by a consumer.

## Where rules belong

- Exact tracked-tree facts—filenames, placement, topology, migrations, pull-request size,
  ownership, delivery/GitHub state, and repository-wide API/document sets—belong here.
- Source and configuration semantics for Python, TypeScript, SQL, Terraform/HCL, Markdown,
  YAML, JSON, and shell belong in `sarj-ai/code-standards`.

## Run it

Sarj repositories should use the single Code Standards setup path. It installs the canonical
staged repository check, managed commit-message check, and authoritative pull-request history
workflow without creating a second Python environment:

```bash
uvx --no-config --isolated --python 3.14 --from code-standards code-standards setup
code-standards doctor
```

Use the current release without installing it:

```bash
uvx --from repo-standards repo-standards pull-request size . --base origin/main
```

For a persistent user installation:

```bash
uv tool install repo-standards
repo-standards pull-request size . --base origin/main
```

Upgrade with `uv tool upgrade repo-standards`. Automation should pin the package version or
the GitHub Action's full commit SHA.

## Safety model

- Repository contents come from one exact Git tree.
- Workflow YAML and API descriptions are parsed as inert data.
- Missing required evidence produces an inconclusive result rather than a false pass.
- Advisory commit-history analysis reports incomplete evidence without blocking local commits.
- The linter has no autofix or repository mutation mode.

## Development

```bash
uv sync --locked
uv run pytest
uv run ruff check .
uv run basedpyright
```

Build the same wheel and source distribution used by publishing:

```bash
uv build --no-sources
```

Releases are reconcilable. The protected workflow independently repairs a missing PyPI
publication or GitHub Release from the same verified source revision.

## GitHub Action

```yaml
- uses: sarj-ai/repo-standards@298d09a504ef3dea39c29cedc315fffc62b61d11 # v6.23.1
```
