quickbot_cli
QuickBot CLI for scaffolding new projects from templates.
Features
- Generate a ready-to-run QuickBot app structure from templates
- Optional modules (e.g., Alembic migrations, i18n) included/excluded via flags
Installation
You can install the CLI into your environment:
uv pip install quickbot-cli
Alternatively, for local development in this repo:
uv pip install -e .[dev]
Usage
Show help:
uv run quickbot --help
uv run quickbot init --help
Generate a project into a target directory (default template: "basic"):
uv run quickbot init ./my_bot \
--template basic \
--project-name my_bot \
--description "My awesome bot" \
--author "Jane Doe" \
--license-name MIT \
--include-alembic \
--include-i18n \
--overwrite
Key options:
--template, -t: template name (default:basic)--project-name: project name used during rendering--description: short description--author: author name--license-name: license identifier (e.g., MIT)--include-alembic/--no-include-alembic: include Alembic files (default: on)--include-i18n/--no-include-i18n: include i18n files (default: on)--overwrite: overwrite existing files when rendering
Templates
Built-in templates live under src/quickbot_cli/templates/. The default is basic and includes a minimal app layout plus optional Alembic/i18n modules.
Each template can include a __template__.yaml file describing variables and post-generation tasks. Example:
variables:
project_name:
prompt: Project name
default: my_project
include_alembic:
prompt: Include Alembic?
choices: ["yes", "no"]
default: "yes"
post_tasks:
- when: "{{ include_alembic }}"
run: ["echo", "alembic_initialized"]
Template files use the .j2 suffix and are rendered to the output path with variables made available to Jinja2. Non-.j2 files are copied as-is.
Development
Clone the repo and install dev deps:
uv pip install -e .[dev]
Run tests:
uv run python run_tests.py
# or
uv run -m pytest tests/ -v --tb=short
Code style and tooling:
- Ruff and MyPy configs are in
pyproject.toml - Pre-commit hooks:
.pre-commit-config.yaml
License
MIT. See LICENSES/MIT.txt.
Metadata
Release files for quickbot-cli 0.1.1
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 | Actions |
|---|---|---|---|---|
| quickbot_cli-0.1.1.tar.gz | 13.5 kB | Without provenance | Details for quickbot_cli-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| quickbot_cli-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for quickbot_cli-0.1.1-py3-none-any.whl |
Total release size: 29.7 kB
Release files / quickbot_cli-0.1.1.tar.gz
| Download URL | quickbot_cli-0.1.1.tar.gz |
|---|---|
| Size | 13.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2feb3e3cca1923f86c2f056c0cd6bece07f9a1dccf72577b662884e7d2f44c5e
|
|
BLAKE2b-256 checksum How to use checksums |
f0abfb9d6733fefbccba493dcfdb824511c06442189444609ba4cf50990364ad
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.15
|
Release files / quickbot_cli-0.1.1-py3-none-any.whl
| Download URL | quickbot_cli-0.1.1-py3-none-any.whl |
|---|---|
| Size | 16.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6203352ac1ec0c78c669eb1d86128892d3420c5351991afc9c18561f77d28e22
|
|
BLAKE2b-256 checksum How to use checksums |
cecbe307c917565d903f81ffe6c0bfe6e1a2e7e0adee787c4c686b979e76c030
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.15
|
Security for quickbot-cli 0.1.1
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.