Open source A workflow for AI-written code

Build with AI.
Keep what passes.

AI speed. Engineering discipline.

Getzilla lets an AI write code for your project and checks that code before it is allowed to stay.

  • Free and open source
  • MIT license
  • Your agent. Your models.

The short version

Keep the fast part.
Add the checking part.

The AI still builds what you asked for. Before that work joins the real project, tests run, a different AI reviews it, and required checks decide whether it can merge.

Vibe coding vs. Getzilla
What changesPlain vibe codingWith Getzilla
“It works”The AI says soTests and checks ran. Results are saved.
Who reviewsThe same AI that wrote itA different AI reviewer. The author cannot approve itself.
Where work goesSometimes straight into mainA branch and a pull request for each task.
MemoryGone when the chat endsThe request, plan, test results and reviews stay with the task.
Small vs. risky workThe same pathA short path for small changes. More checks for risky work.
Who shipsThe AIWhen configured to do so, the agent merges after required checks and independent review.

Required checks and branch protection must be configured to enforce merge rules.* Local reports alone cannot prevent a merge. Enforcement needs GitHub branch protection that requires the Getzilla check or Trust CI.

How a task goes

Vibe first.
Check second.

Build the feature on its own branch. Then put the working result through Getzilla before it is kept.

  1. 01

    Build it

    Get the feature working quickly on its own branch.

  2. 02

    Sort it

    Choose the skills, reviewers and level of care the task needs. Ask a person to approve the plan when required.

  3. 03

    Check it

    Run tests and other checks. Save the results next to the task.

  4. 04

    Review it

    Separate AI reviewers read the change and record their findings.

  5. 05

    Ship it

    Open a pull request. The agent can merge when required checks pass on the same commit, independent review passes and review threads are resolved.

The next session starts with context.

Each task leaves its request, plan, results and reviews. Lessons go into mistakes.md and decisions.md, so the next session can use them.

A check outside the author

The author cannot
approve itself.

A different AI reviewer checks the change.* Teams can add Trust CI, a separate service that checks the exact version again before merge.

Public code

GitHub Actions supplies the repository gate. Getzilla can add a pinned, read-only workflow with one command.

python3 scripts/getzilla_ci.py --write

Private code

Trust CI runs on dedicated hardware. Access is paid and priced on request, per GitHub account.

See access options

Explicit conditions

Required checks must pass on the same commit, review must be independent, and review threads must be resolved. Production changes and security approvals still need a person’s decision.

Start from the published release

Install Getzilla.

The installer adds missing Git, Python and your chosen coding agent, downloads Getzilla to ~/Getzilla and checks the machine. Use the command for your operating system.

1. Download, verify, then run

The commands below match the current README. They pin the release and verify the installer’s SHA-256 before it runs.

Windows · PowerShell
$f = Join-Path $env:TEMP 'getzilla-install.ps1'
Invoke-WebRequest -UseBasicParsing https://raw.githubusercontent.com/Dimkox/Getzilla/v2.3.0/scripts/install.ps1 -OutFile $f
if ((Get-FileHash $f -Algorithm SHA256).Hash -eq '4D89D8C77617FF3B262BBF8866F05E1A14D9FB45C6BA2C3C39E298AF9A499B76') { $env:GETZILLA_REF = 'v2.3.0'; Invoke-Expression (Get-Content -Raw $f) } else { throw 'install.ps1 SHA-256 mismatch: do not run it' }
Linux · Bash
curl -fsSLo getzilla-install.sh https://raw.githubusercontent.com/Dimkox/Getzilla/v2.3.0/scripts/install.sh
echo "aa10c167d02aa8633f0d0d4478b9c0ad0fac3122ef293f633f1075f218889807  getzilla-install.sh" | sha256sum -c - && GETZILLA_REF=v2.3.0 bash getzilla-install.sh
macOS · Bash
curl -fsSLo getzilla-install.sh https://raw.githubusercontent.com/Dimkox/Getzilla/v2.3.0/scripts/install.sh
echo "aa10c167d02aa8633f0d0d4478b9c0ad0fac3122ef293f633f1075f218889807  getzilla-install.sh" | shasum -a 256 -c - && GETZILLA_REF=v2.3.0 bash getzilla-install.sh

On Windows, PowerShell 7.4 or newer is required. Windows PowerShell 5.1 can start the installer; it adds the newer version with winget. If verification fails, do not run the downloaded file.

3. Take the read-only tour

From the Getzilla folder, open the browser tour. On Windows, use py -3 instead of python3.

python3 scripts/getzilla_demo.py --open

4. Ask for a plan for your project

This command reads the target project and changes nothing. Review its plan, then follow the Quick start.

python3 scripts/install_into.py --plan /absolute/path/to/your/repo
Continue with Quick start

What it costs

Getzilla is free.
Choose your check.

Public repositories use GitHub Actions. Private repositories use Trust CI on dedicated hardware. Model usage belongs to your own agent account or API key.

Public repositories

Free

Open source and side projects

  • Getzilla workflow under the MIT license
  • Repository gate on GitHub Actions
  • Pinned, read-only workflow
  • Tests, saved evidence and independent AI review
Install Getzilla

Make the next change clearer

Practical checks.
Working examples.

Explore guides, service scoping notes and downloadable worksheets for an existing codebase.

Scope a change

Define the problem, acceptance evidence and limits of a repository task.