augint-mono
CLI tools for coordinating monorepos with git submodules.
Installation
uv add --dev augint-mono
Usage
ai-mono status # Cross-repo status dashboard
ai-mono sync [--commit] # Sync submodule pointers to latest
ai-mono init # First-time submodule setup
ai-mono health # Cross-repo health analysis
ai-mono foreach <cmd> # Run shell command in each submodule
Limitations
ai-mono foreach runs shell commands only. AI agent skills (invoked as /skill-name in agent UIs) are handled by the AI agent, not by the shell, so they cannot be delegated through foreach. To run a skill across submodules, the AI agent must iterate over them itself -- this is what the ai-mono-foreach skill in augint-shell does.
Submodule Branch Tracking
Each submodule should have a branch configured in .gitmodules so that ai-mono sync knows which branch to track:
# IaC repos (dev-to-main workflow) should track dev
git config -f .gitmodules submodule.backend.branch dev
# Library repos (main-only) should track main
git config -f .gitmodules submodule.shared-lib.branch main
Metadata
Release files for augint-mono 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| augint_mono-0.1.4.tar.gz | 8.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| augint_mono-0.1.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 22.1 kB
Release files / augint_mono-0.1.4.tar.gz
| Download URL | augint_mono-0.1.4.tar.gz |
|---|---|
| Size | 8.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
617727f5d9f01de4ae56d135d519c19441ef4af3c9a8d3cbac3f8b78e1394386
|
|
BLAKE2b-256 checksum How to use checksums |
98b2bab7b3594e62dd2f65fac5621176ee7183a8d518ac4981439a3e66177497
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Apr 5, 2026.
Transparency logRelease files / augint_mono-0.1.4-py3-none-any.whl
| Download URL | augint_mono-0.1.4-py3-none-any.whl |
|---|---|
| Size | 13.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
52ebb37bcb721b0cbf021fbde0da3b09e5a9fc15550de933d53f96ca7d7b1af2
|
|
BLAKE2b-256 checksum How to use checksums |
3b9955516a9a17d0899d1dfbefc0e869f619f19e573769d144bb0c694c5e52d4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Apr 5, 2026.
Transparency log