allfly-crew
allfly-crew is Allfly's unified AI toolset: a home for company-wide automation
built on crewAI and AWS Bedrock, designed so
new capabilities can be added over time without restructuring.
The first feature is PR/code review: crewAI agents that read a project's review standards and a git diff, then produce structured findings (file, line, severity, comment). It ships in two modes:
diff— a single generalist reviewer, driven byreview_criteria.md.categorized— one specialist agent per rule category (one subdirectory of.mdrule files = one category), run concurrently viaasyncio.gather, each scoped to only its own category's rules.
Layout
src/allfly_crew/
├── main.py # top-level entrypoint, dispatches to sub-crews
├── reviews/ # the PR/code review sub-crew
│ ├── crew.py # diff mode (single generalist reviewer)
│ ├── categorized_review.py # categorized mode (specialist agents)
│ ├── config/ # agents.yaml / tasks.yaml for diff mode
│ ├── standards/ # universal rule content (future)
│ └── tools/
│ └── git_diff_tool.py
├── architecture/ # placeholder for a future sub-crew
└── devops/ # placeholder for a future sub-crew
Usage
uv sync
# Single-reviewer diff mode
uv run python -m allfly_crew.main reviews diff <repo_path> <base_ref> [head_ref]
# Categorized mode: one specialist reviewer per rules_dir subdirectory
uv run python -m allfly_crew.main reviews categorized <rules_dir> <repo_path> <base_ref> [head_ref]
Requires AWS Bedrock credentials and a BEDROCK_MODEL_ID environment variable
(see .env.example).
More sub-crews (architecture, devops, ...) and a universal rule-selection model
(allfly-crew.toml) are planned; see prompt.md for the full roadmap.
Installing as a CLI
Once published to PyPI, install as a standalone tool (no venv activation needed):
uv tool install allfly-crew
# or
pipx install allfly-crew
allfly-crew reviews diff <repo_path> <base_ref> [head_ref]
Release Procedures
- This project uses "trunk" based development off of
master. - PRs are allowed but always folded back to
master. - To release: go to the repo's Actions tab, run the Publish workflow, and
choose a bump type (
patch,minor,major). It bumps the version inpyproject.toml, tags the release, builds withuv build, publishes to PyPI, and creates a GitHub release.
Metadata
Release files for allfly-crew 0.0.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 | Actions |
|---|---|---|---|---|
| allfly_crew-0.0.2.tar.gz | 251.4 kB | With provenance | Details for allfly_crew-0.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| allfly_crew-0.0.2-py3-none-any.whl | Python 3 | none | any | Details for allfly_crew-0.0.2-py3-none-any.whl |
Total release size: 264.5 kB
Release files / allfly_crew-0.0.2.tar.gz
| Download URL | allfly_crew-0.0.2.tar.gz |
|---|---|
| Size | 251.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
849518cfd3a17831ccc38d583018bc7771e65a9de1fcd1b2beb597a52582441e
|
|
BLAKE2b-256 checksum How to use checksums |
74cd759ad10eb0e7871c47ea9066462fff87172657100455f70be93b85943597
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 3, 2026.
Transparency logRelease files / allfly_crew-0.0.2-py3-none-any.whl
| Download URL | allfly_crew-0.0.2-py3-none-any.whl |
|---|---|
| Size | 13.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c12bd1d991d21258cae2e6b2807fc1d67f8e1427bc26101812bd73dd47f38701
|
|
BLAKE2b-256 checksum How to use checksums |
09be022b3ba8057ae1f1f78dfb4316545f07b07fc16c04b9573c085564124e14
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 3, 2026.
Transparency logSecurity for allfly-crew 0.0.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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for allfly_crew-0.0.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 3, 2026.
Transparency logA 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.