ANTIGRAVITY LABJP
TAG

CI

9 articles
Back to all tags
Related:
Antigravity4automation4migration3Agents2antigravity-cli2antigravity2Antigravity CLI2Gemini CLI2Configuration1Permissions1Performance1ORM1
Agents/2026-07-29Advanced

A Typo in agent.md Quietly Widened My Permissions — Writing a Strict Frontmatter Lint

Misspelled keys in agent.md frontmatter do not raise errors. They fall back to defaults, and for permission fields that fallback points the wrong way. Here is the failure I hit, the lint I wrote to catch it, and what the measurements showed.

App Dev/2026-07-10Advanced

An Agent's ORM Code Made p95 Five Times Slower — Measuring Query Counts and Blocking Them in CI

N+1 queries slip past code review because the code looks correct. Here is a CI gate that measures query counts and judges them by their slope against input size, with working code and real numbers.

Agents/2026-07-10Advanced

When Your Agent's Files Vanish Into .gitignore — A Pre-Commit Detection Gate

When an agent writes files that match .gitignore, the diff review looks perfect but nothing lands in the commit. Here is a gate script that catches ignored build output before you push, plus the tuning it needs.

App Dev/2026-06-24Advanced

Running Pre-Release Checks Without Opening the IDE — Designing the Android CLI as the Verification Gate of an Unattended Pipeline

How to slot Android CLI v1.0 into an unattended pipeline as its verification gate — three layers of checks, an exit-code contract, and a density-by-locale matrix, sized for an indie developer's day-to-day.

Integrations/2026-06-19Intermediate

From Gemini CLI to Antigravity CLI: Migrating Without Stopping Your Automation

Gemini CLI has been retired and the Go-rewritten Antigravity CLI is now its successor. If you have the CLI wired into CI or scheduled jobs, swapping everything at once will break your automation. Here is a concrete plan for migrating gradually, from parallel testing to full cutover.

Integrations/2026-06-18Advanced

On Cutover Day to the Antigravity CLI, Verify Production Automation by Side-Effect Equivalence, Not Output

On the day you switch from the Gemini CLI to the Antigravity CLI, verify production automation by the equivalence of side effects — files written, commits, network calls — instead of matching stdout. A sandbox parallel run and a go/no-go cutover gate, with implementation steps.

Antigravity/2026-06-16Advanced

Does the New CLI Do the Same Job? An Output-Parity Gate Before Switching to Antigravity CLI

With Gemini CLI shutting down on June 18, here is how I froze the old CLI's artifacts as a golden baseline and built a parity harness to catch regressions before cutting over to Antigravity CLI — with normalization and a go/no-go gate, in code.

Integrations/2026-06-15Advanced

Regression-Testing Antigravity Agent Output in CI

Agent output drifts between identical runs and turns CI red for no real reason. Here is how I stabilized snapshot regression testing for Antigravity agents using a normalization layer and pytest golden files, drawn from running it in my own indie developer CI.

Antigravity/2026-06-14Intermediate

A Compatibility Shim That Bridges Old Scripts to agy Before Gemini CLI Shuts Down

Ahead of the June 18 Gemini CLI shutdown, instead of rewriting every gemini call scattered across cron and CI at once, a thin compatibility shim can bridge them to the Antigravity CLI (agy). Here is the approach with working shell scripts.