Thanks for improving Antigravity. The project direction is a repository knowledge engine first; plugins, MCP, and templates are delivery paths around that core.
- Read
README.mdandVERSIONING.md. - For behavior changes, add or update focused tests.
- Keep docs aligned when you change install flows, environment variables, supported Python versions, or plugin commands.
python3 -m venv venv
source venv/bin/activate
pip install -e ./cli -e './engine[dev]'Run the checks that match your change:
python scripts/check_repo_contract.py
pytest engine/tests cli/testsFor Docker changes:
docker compose config --quiet
docker build -t antigravity-local .
docker build -f Dockerfile.sandbox -t antigravity-sandbox-local .Engine, CLI, and plugin versions may advance independently. Plugin metadata must
stay aligned across Claude Code, Claude marketplace, and Codex manifests. See
VERSIONING.md before changing versions.
Use a narrow scope. Explain the user-visible contract you changed, list the checks you ran, and call out any skipped checks with the reason.