Gator Command
Git-native governance for AI-assisted engineering.
Gator turns your repo into an intelligence surface. The AI agent builds structured maps of your codebase (charters), a strategic operations brief (pulse), and project assessments — all committed to Git. A deterministic pre-commit gate blocks commits when the agent changes code without updating the map.
Local-first. Git-native. Works with Claude Code, Codex, Gemini CLI. Apache 2.0 licensed.
Install
pip install pipx # if you don't have pipx yet
pipx ensurepath # add to PATH (restart terminal after)
pipx install gator-command
Quick Start
cd /path/to/your/repo
gator gatorize . # install governance into this repo
gator init # start a governed session
gator dashboard # open the intelligence console
The agent reads the governance layer and orients to your project. Your first git commit fires the hooks.
Upgrade
pipx upgrade gator-command
cd /path/to/your/repo
gator gatorize . # refresh templates and hooks
Your content is always preserved. Only templates and scripts refresh.
Commands
| Command | What it does |
|---|---|
gator gatorize <path> |
Install or upgrade governance in a repo |
gator init |
Start a governed session (repairs hooks if needed) |
gator dashboard |
Open the intelligence console |
gator pulse |
Generate the strategic operations brief |
gator audit |
Run governance audit |
gator version |
Show installed version |
What Gator Provides
- Repo intelligence — charters map code structure, pulse summarizes momentum, assessments provide AI-generated evaluation. All committed to Git.
- Governance enforcement — a deterministic pre-commit hook that blocks commits when code changes without charter updates. No LLM in the gate. Configurable: strict, warn, or off.
- Dashboard — a local web console for browsing your governance layer, session history, and project state. Full file history with git version navigation.
- Session persistence — the governance layer carries project context across sessions and across models. Switch from Claude to Codex mid-project without losing architectural understanding.
How It Works
gator gatorize .installs a.gator/folder into your repo with governance scaffolding- AI agents read the constitution and charters to understand your codebase
- Every
git commitruns a deterministic hook that validates charter-alongside-code - Session snippets capture what context produced each commit
gator dashboardmakes it all browsable in a local web UI
Links
Built by Cumberland Laboratories
1 maintainer
Release files for gator-command 2.13.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gator_command-2.13.2-py3-none-any.whl | Python 3 | none | any | Details |
Release files / gator_command-2.13.2-py3-none-any.whl
| Download URL | gator_command-2.13.2-py3-none-any.whl |
|---|---|
| Size | 582.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a004e4644ee21c32491c300d501163b88ce5051a149d7ec74f555c5d8599436a
|
|
BLAKE2b-256 checksum How to use checksums |
c402af5674f8804912f3127458343da7310e0b82db4414900c6cacc4f7e0ae79
|
| 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 Sep 12, 2026.
Transparency log
