bazis-cli 2.4.0__tar.gz

bazis_cli-2.4.0/.dockerignore

@@ -0,0 +1,3 @@
+.gitlab-ci.yml
+.gitignore
+.dockerignore

bazis_cli-2.4.0/.github/workflows/build-publish.yml

@@ -0,0 +1,20 @@
+name: Build and Publish
+
+on:
+  push:
+    tags:
+      - 'v*.*.*'
+  # started by the Release workflow on the tag it creates: a tag pushed with the
+  # workflow token does not trigger the push event above
+  workflow_dispatch:
+
+permissions:
+  contents: write
+
+jobs:
+  build:
+    if: startsWith(github.ref, 'refs/tags/v')
+    uses: ecofuture-tech/.github/.github/workflows/reusable-build-publish.yml@main
+    secrets:
+      PYPI_TOKEN: ${{ secrets.PYPI_TOKEN }}
+      TEST_PYPI_TOKEN: ${{ secrets.TEST_PYPI_TOKEN }}

bazis_cli-2.4.0/.github/workflows/release.yml

@@ -0,0 +1,77 @@
+name: Release
+
+# Creates the release tag vX.Y.Z on the current main commit and starts Build and Publish
+# for it. Run it from the Actions tab (or through the GitHub API) on the main branch.
+
+on:
+  workflow_dispatch:
+    inputs:
+      version:
+        description: 'Version without the "v" prefix, e.g. 2.3.0 or 2.4.0-rc1'
+        required: true
+        type: string
+
+permissions:
+  contents: write
+  actions: write
+
+concurrency:
+  group: release
+  cancel-in-progress: false
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    if: github.ref == 'refs/heads/main'
+    env:
+      GH_TOKEN: ${{ github.token }}
+      VERSION: ${{ inputs.version }}
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Validate the version
+        run: |
+          if [[ ! "$VERSION" =~ ^[0-9]+\.[0-9]+\.[0-9]+(-(alpha|beta|rc)[0-9]+)?$ ]]; then
+            echo "::error::Invalid version '$VERSION', expected e.g. 2.3.0 or 2.4.0-rc1"
+            exit 1
+          fi
+          if git rev-parse -q --verify "refs/tags/v$VERSION" >/dev/null; then
+            echo "::error::Tag v$VERSION already exists"
+            exit 1
+          fi
+          # versionsort.suffix: a pre-release (v2.4.0-rc1) sorts before its release (v2.4.0)
+          LAST_TAG=$(git -c versionsort.suffix=- tag --list 'v*' --sort=-v:refname | head -n 1)
+          echo "Last release: ${LAST_TAG:-none}, new release: v$VERSION"
+          # sort -V orders "~" before anything, as versionsort.suffix does with "-"
+          NEWEST=$(printf '%s\n%s\n' "${LAST_TAG#v}" "$VERSION" | sed 's/-/~/' | sort -V | tail -n 1)
+          if [ -n "$LAST_TAG" ] && [ "$NEWEST" != "${VERSION/-/\~}" ]; then
+            echo "::error::Version $VERSION is not newer than $LAST_TAG"
+            exit 1
+          fi
+
+      - name: Require green tests on this commit
+        run: |
+          CONCLUSION=$(gh run list --workflow tests.yml --commit "$GITHUB_SHA" --status completed \
+            --json conclusion --jq 'map(.conclusion) | first // "none"')
+          echo "Tests on $GITHUB_SHA: $CONCLUSION"
+          if [ "$CONCLUSION" != "success" ]; then
+            echo "::error::The Tests workflow has not succeeded on $GITHUB_SHA ($CONCLUSION)"
+            exit 1
+          fi
+
+      - name: Create the tag
+        run: |
+          git config user.name 'github-actions[bot]'
+          git config user.email '41898282+github-actions[bot]@users.noreply.github.com'
+          git tag -a "v$VERSION" -m "${{ github.event.repository.name }} $VERSION" "$GITHUB_SHA"
+          git push origin "v$VERSION"
+
+      - name: Start Build and Publish
+        run: gh workflow run build-publish.yml --ref "v$VERSION"
+
+      - name: Summary
+        run: |
+          echo "Tagged \`v$VERSION\` at \`$GITHUB_SHA\` and started Build and Publish." >> "$GITHUB_STEP_SUMMARY"

bazis_cli-2.4.0/.github/workflows/tests.yml

@@ -0,0 +1,60 @@
+name: Tests
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+
+permissions:
+  contents: read
+
+concurrency:
+  group: tests-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v6
+      - run: uvx ruff check bazis tests
+
+  tests:
+    name: tests (python ${{ matrix.python }}, ${{ matrix.resolution }})
+    runs-on: ubuntu-latest
+    timeout-minutes: 30
+    strategy:
+      fail-fast: false
+      matrix:
+        python: ['3.12', '3.13', '3.14']
+        resolution: [highest]
+        include:
+          # the lowest versions allowed by pyproject.toml
+          - python: '3.12'
+            resolution: lowest-direct
+
+    # the tests build a project and check it without PostgreSQL or Redis: no services
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install GDAL (required by the PostGIS database backend)
+        # a stalled Ubuntu mirror must fail the step quickly instead of hanging the job
+        timeout-minutes: 10
+        run: |
+          APT="sudo apt-get -o Acquire::Retries=3 -o Acquire::http::Timeout=30 -o Acquire::https::Timeout=30"
+          $APT update
+          $APT install -y --no-install-recommends gdal-bin
+
+      - uses: astral-sh/setup-uv@v6
+        with:
+          python-version: ${{ matrix.python }}
+          activate-environment: true
+
+      - name: Install dependencies
+        run: uv pip install --resolution ${{ matrix.resolution }} -e '.[test]'
+
+      - name: Run tests
+        run: python -m pytest tests -p no:cacheprovider

bazis_cli-2.4.0/.github/workflows/update-licenses.yml

@@ -0,0 +1,18 @@
+name: Update Licenses
+
+on:
+  push:
+    branches:
+      - main
+    paths:
+      - '**.py'
+      - 'pyproject.toml'
+
+permissions:
+  contents: write
+
+jobs:
+  update-licenses:
+    uses: ecofuture-tech/.github/.github/workflows/reusable-update-licenses.yml@main
+    secrets:
+      WORKFLOW_LICENSE_TOKEN: ${{ secrets.WORKFLOW_LICENSE_TOKEN }}

bazis_cli-2.4.0/.gitignore

@@ -0,0 +1,44 @@
+.idea
+.ipynb_checkpoints
+.mypy_cache
+.vscode
+__pycache__
+.pytest_cache
+htmlcov
+dist
+site
+.coverage
+coverage.xml
+.netlify
+test.db
+log.txt
+Pipfile.lock
+env3.*
+env
+docs_build
+venv
+.venv
+docs.zip
+archive.zip
+
+.env
+local.env
+*/.env*
+
+# vim temporary files
+*~
+.*.sw?
+*.DS_Store
+
+*.egg-info
+build
+dist
+
+docs/_autosummary
+docs/_build
+*.DS_Store
+*.log
+my-*
+My*
+*/**/_version.py
+/uv.lock

bazis_cli-2.4.0/CLAUDE.md

@@ -0,0 +1,47 @@
+# bazis-cli
+
+The `bazis` command (`bazis new`, `bazis add`, `bazis audit`): Claude Code through the
+Claude Agent SDK, run in a Bazis project with the MCP server bazis-mcp and the rules of
+Bazis (`agent.RULES`).
+
+- `bazis/contrib/cli/main.py` — the commands and their prompts;
+- `bazis/contrib/cli/agent.py` — the options of the agent (tools, permissions, MCP server),
+  the permission prompt in the terminal and the output;
+- `bazis/contrib/cli/scaffold.py` — the skeleton of a new project and its `.venv`.
+
+Commits, tags and pull requests are authored by the maintainer, Ilya Kharyn
+<ilya.tt07@gmail.com>, never by an AI assistant (see the CLAUDE.md of the core).
+
+## Running the tests
+
+The tests replace the Claude Agent SDK with a fake: they spend no credits and need no
+account. The scaffold test runs `bazis_doctor` in a generated project (GDAL is needed for
+the PostGIS backend; neither PostgreSQL nor Redis):
+
+```bash
+python -m pytest tests -p no:cacheprovider
+```
+
+Lint: `ruff check bazis tests`. A real run (`bazis audit --budget 0.5` in a project) spends
+credits of the Claude Code account: do it only when asked.
+
+## Releasing
+
+A release is the tag `vX.Y.Z` on `main`: the Build and Publish workflow builds the package
+(the version comes from the tag through setuptools-scm) and publishes it to PyPI
+(pre-releases `-alphaN`/`-betaN`/`-rcN` go to Test PyPI) and creates the GitHub release.
+
+Claude Code sessions cannot push tags. Release through the **Release** workflow instead:
+
+1. Make sure the changes are merged into `main` and the Tests workflow is green on the
+   `main` head commit (the Release workflow checks this and refuses otherwise).
+2. Add the release notes as `docs/releases/X.Y.Z.md` in the change being released.
+3. Start the workflow `release.yml` on `ref: main` with the input `version: X.Y.Z`
+   (GitHub API: `POST /repos/ecofuture-tech/bazis-cli/actions/workflows/release.yml/dispatches`;
+   with the GitHub MCP tools: `actions_run_trigger`, method `run_workflow`).
+4. The Release run creates the annotated tag and starts Build and Publish on it. Check
+   that both runs succeed and that the version appears on https://pypi.org/project/bazis-cli/.
+
+bazis-cli is released after bazis-mcp. Pick the version by semver: breaking changes
+(commands or options renamed or removed) bump the minor version while the project is
+below 3.0.

bazis_cli-2.4.0/PKG-INFO

@@ -0,0 +1,93 @@
+Metadata-Version: 2.4
+Name: bazis-cli
+Version: 2.4.0
+Summary: The bazis command: creates, extends and audits Bazis projects with Claude (Claude Agent SDK).
+Author-email: Ilya Kharyn <ilya.tt07@gmail.com>
+Maintainer-email: Ilya Kharyn <ilya.tt07@gmail.com>
+License-Expression: Apache-2.0
+Project-URL: Home, https://github.com/ecofuture-tech/bazis-cli
+Keywords: bazis,django,fastapi,pydantic,framework,jsonapi,cli,ai,agents,claude
+Classifier: Intended Audience :: Developers
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Framework :: Django
+Classifier: Framework :: FastAPI
+Requires-Python: >=3.12
+Description-Content-Type: text/markdown
+Requires-Dist: bazis-mcp>=2.4.1
+Requires-Dist: claude-agent-sdk>=0.2.163
+Provides-Extra: test
+Requires-Dist: pytest>=8; extra == "test"
+Provides-Extra: dev
+Requires-Dist: ruff; extra == "dev"
+
+# bazis-cli
+
+The `bazis` command creates, extends and audits [Bazis](https://github.com/ecofuture-tech/bazis)
+projects with Claude. It runs Claude Code (the [Claude Agent SDK](https://code.claude.com/docs/en/agent-sdk))
+in the project with the MCP server [bazis-mcp](https://github.com/ecofuture-tech/bazis-mcp),
+so the agent chooses the Bazis packages from their catalog, follows their guides and checks
+the result with the system checks of the project instead of relying on its memory.
+
+## Installation
+
+```bash
+pip install bazis-cli      # or: uv tool install bazis-cli
+claude login               # or set ANTHROPIC_API_KEY
+```
+
+The agent uses the account of Claude Code and spends its credits; limit a run with
+`--budget`.
+
+## Commands
+
+```bash
+# a new project from a description
+bazis new shop "An online shop: products with categories, orders of users, \
+users see only their own orders"
+
+# a Bazis package for an existing project (run in the directory of manage.py)
+bazis add bazis-statusy "orders go through new -> paid -> shipped"
+
+# a review against the guides and checks of the packages; --fix also fixes
+bazis audit
+bazis audit --fix
+```
+
+- `bazis new DIR DESCRIPTION` writes the skeleton of a project: the project package
+  (settings, root router, ASGI app), `project.env`, `.env` with a generated secret key,
+  `requirements.txt`, `requirements-dev.txt`, `tests/`, `.mcp.json` and `AGENTS.md`. It
+  creates `.venv` with Bazis and bazis-mcp (with uv if it is installed; `--no-venv` skips
+  it). Then the agent chooses the Bazis packages, creates the apps, models, routes,
+  migrations and tests, and runs the checks.
+- `bazis add PACKAGE [GOAL]` installs a Bazis package with the Bazis packages it requires
+  and sets them up as their guides say.
+- `bazis audit [--fix]` reports the problems of the project by severity. Without `--fix`
+  the agent can only read.
+
+Options of every command: `--project-dir` (`add`, `audit`; default: the current
+directory), `--model` (default `claude-opus-5-5`), `--effort` (`low` ... `max`, default
+`high`), `--budget USD`, `--yes`.
+
+## Permissions
+
+- The agent edits the files of the project directory without asking.
+- Everything else is shown in full and asked in the terminal: every shell command
+  (installing packages, migrations, tests), edits and reads outside the project, web access.
+  `y` allows it, `a` allows the rest of the run. `--yes` allows all of it; without a
+  terminal and without `--yes` it is denied.
+- The agent cannot read `.env` and cannot commit, push or reset with git: review the changes
+  and commit them yourself.
+- Only the settings of bazis-cli apply: the Claude Code settings, hooks and MCP servers of
+  the project and of the user are not loaded.
+- `bazis audit` without `--fix` can only read the project and call bazis-mcp. bazis-mcp
+  runs the system checks of the project, that is the project code with its `.venv`: run
+  the commands only in projects you trust.
+
+The tests of a project need PostgreSQL with PostGIS and Redis (settings in `.env`); without
+them the agent creates the migrations and runs the system checks, and says that the tests
+did not run.

bazis_cli-2.4.0/README.md

@@ -0,0 +1,66 @@
+# bazis-cli
+
+The `bazis` command creates, extends and audits [Bazis](https://github.com/ecofuture-tech/bazis)
+projects with Claude. It runs Claude Code (the [Claude Agent SDK](https://code.claude.com/docs/en/agent-sdk))
+in the project with the MCP server [bazis-mcp](https://github.com/ecofuture-tech/bazis-mcp),
+so the agent chooses the Bazis packages from their catalog, follows their guides and checks
+the result with the system checks of the project instead of relying on its memory.
+
+## Installation
+
+```bash
+pip install bazis-cli      # or: uv tool install bazis-cli
+claude login               # or set ANTHROPIC_API_KEY
+```
+
+The agent uses the account of Claude Code and spends its credits; limit a run with
+`--budget`.
+
+## Commands
+
+```bash
+# a new project from a description
+bazis new shop "An online shop: products with categories, orders of users, \
+users see only their own orders"
+
+# a Bazis package for an existing project (run in the directory of manage.py)
+bazis add bazis-statusy "orders go through new -> paid -> shipped"
+
+# a review against the guides and checks of the packages; --fix also fixes
+bazis audit
+bazis audit --fix
+```
+
+- `bazis new DIR DESCRIPTION` writes the skeleton of a project: the project package
+  (settings, root router, ASGI app), `project.env`, `.env` with a generated secret key,
+  `requirements.txt`, `requirements-dev.txt`, `tests/`, `.mcp.json` and `AGENTS.md`. It
+  creates `.venv` with Bazis and bazis-mcp (with uv if it is installed; `--no-venv` skips
+  it). Then the agent chooses the Bazis packages, creates the apps, models, routes,
+  migrations and tests, and runs the checks.
+- `bazis add PACKAGE [GOAL]` installs a Bazis package with the Bazis packages it requires
+  and sets them up as their guides say.
+- `bazis audit [--fix]` reports the problems of the project by severity. Without `--fix`
+  the agent can only read.
+
+Options of every command: `--project-dir` (`add`, `audit`; default: the current
+directory), `--model` (default `claude-opus-5-5`), `--effort` (`low` ... `max`, default
+`high`), `--budget USD`, `--yes`.
+
+## Permissions
+
+- The agent edits the files of the project directory without asking.
+- Everything else is shown in full and asked in the terminal: every shell command
+  (installing packages, migrations, tests), edits and reads outside the project, web access.
+  `y` allows it, `a` allows the rest of the run. `--yes` allows all of it; without a
+  terminal and without `--yes` it is denied.
+- The agent cannot read `.env` and cannot commit, push or reset with git: review the changes
+  and commit them yourself.
+- Only the settings of bazis-cli apply: the Claude Code settings, hooks and MCP servers of
+  the project and of the user are not loaded.
+- `bazis audit` without `--fix` can only read the project and call bazis-mcp. bazis-mcp
+  runs the system checks of the project, that is the project code with its `.venv`: run
+  the commands only in projects you trust.
+
+The tests of a project need PostgreSQL with PostGIS and Redis (settings in `.env`); without
+them the agent creates the migrations and runs the system checks, and says that the tests
+did not run.

bazis_cli-2.4.0/bazis/contrib/cli/AGENTS.md

@@ -0,0 +1,33 @@
+# bazis-cli — guide for AI agents
+
+The command `bazis` creates, extends and audits Bazis projects with Claude: it runs Claude
+Code (Claude Agent SDK) in the project with the MCP server bazis-mcp and the rules of
+Bazis. It is a tool for the developer's machine, not a dependency of a project.
+
+## Commands
+
+- `bazis new DIR "what the project does"` writes the skeleton of a project (package with
+  settings, root router and ASGI app, `project.env`, `.env` with a generated secret key,
+  `requirements*.txt`, `tests/`, `.mcp.json`, `AGENTS.md`), creates `.venv` with Bazis and
+  bazis-mcp (`--no-venv` skips it), then the agent chooses the Bazis packages and builds the
+  apps, migrations and tests.
+- `bazis add PACKAGE ["what for"]` installs a Bazis package and its Bazis dependencies and
+  sets them up as their guides say.
+- `bazis audit [--fix]` reviews the project against the guides and checks of its packages;
+  without `--fix` the agent can only read.
+
+Options: `--project-dir` (default: the current directory), `--model` (default
+`claude-opus-5-5`), `--effort` (default `high`), `--budget USD`, `--yes` (run shell commands
+without asking).
+
+## Rules
+
+- Edits of the files of the project are accepted; every shell command and every other tool
+  call (edits or reads outside the project, web) is asked in the terminal (`a` allows the
+  rest of the run) unless `--yes`; without a terminal and `--yes` they are denied.
+- `.env` cannot be read; git cannot commit, push, reset or rebase: the user reviews and
+  commits the changes.
+- Only the MCP server bazis-mcp and no Claude Code settings of the project or the user are
+  loaded. The checks of bazis-mcp run the project code: use the commands in trusted
+  projects.
+- Credentials are those of Claude Code: `claude login` or `ANTHROPIC_API_KEY`.

bazis_cli-2.4.0/bazis/contrib/cli/__init__.py

@@ -0,0 +1,19 @@
+# Copyright 2026 EcoFuture Technology Services LLC and contributors
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#     http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+try:
+    from importlib.metadata import PackageNotFoundError, version
+    __version__ = version('bazis-cli')
+except PackageNotFoundError:
+    __version__ = 'dev'

bazis_cli-2.4.0/bazis/contrib/cli/_version.py

@@ -0,0 +1,24 @@
+# file generated by vcs-versioning
+# don't change, don't track in version control
+from __future__ import annotations
+
+__all__ = [
+    "__version__",
+    "__version_tuple__",
+    "version",
+    "version_tuple",
+    "__commit_id__",
+    "commit_id",
+]
+
+version: str
+__version__: str
+__version_tuple__: tuple[int | str, ...]
+version_tuple: tuple[int | str, ...]
+commit_id: str | None
+__commit_id__: str | None
+
+__version__ = version = '2.4.0'
+__version_tuple__ = version_tuple = (2, 4, 0)
+
+__commit_id__ = commit_id = 'g2d504c4db'