getzilla
Open source Cleanup for AI-written code

Vibe-code it. Getzilla cleans it up.

AI agents build fast and leave a mess behind. Getzilla tidies up after them, checks every change for real, and keeps anything broken out of your main code.

Try it on your project See how it works
  • Free, MIT license
  • Installs into any git repository
  • Shows a plan before it changes anything
Pull request #12feature/checkout → main

Add new checkout flow

  • Agent: “Done, all tests pass”No test run on record
    Unproven
  • Tests for checkoutNone written
    Missing
  • Old loginBroke for existing accounts, nobody noticed
    Broken
  • ReviewOnly the agent that wrote it looked at it
    None
  • Why it is built this wayNot written down anywhere
    Unknown
  • Change recordWhat it does, why, how to verify it
    Written
  • Tests for checkoutAdded and run on this exact version
    Passing
  • Old loginRe-checked, still works
    Passing
  • ReviewDone by someone other than the author
    Approved
  • Final check outside the agentHidden tests the agent cannot edit
    Verified

Getzilla keeps this out of main until it is fixed.

Every check passed. Safe to merge.

Who it’s for

For anyone whose code is written by AI faster than people can check it

A founder working alone on a laptop late at night

Founders and solo builders

You build your product with AI agents and ship every day. Getzilla makes sure fast does not turn into fragile.

A small team working on laptops around one table

Small teams

Several people and several agents in one codebase. Everyone gets the same simple rule for what is allowed into the main code.

A developer with hands over face in front of a laptop

Whoever maintains it next

Months from now someone has to change this code. Getzilla leaves them tests, notes and reasons instead of guesses.

The problem

What goes wrong after vibe‑coding

Vibe-coding is great for getting something working. The trouble starts the day after, when you have to change it.

A developer grabbing his head in front of a laptopLogin broken after yesterday’s update

“It worked yesterday”

A new feature quietly breaks an old one. You find out from your users, not from your tests.

A tangled pile of wiresWhy is it built like this? No notes.

Nobody knows why it is built this way

The agent made hundreds of decisions and wrote none of them down. Changing anything feels like defusing a bomb.

Code on a dark screenAgent: all tests pass0 tests actually run

“Done, all tests pass”

The agent says so. Nobody checked. Sometimes there are no tests, sometimes the agent edited them until they passed.

A wall covered in sticky notesTODO: fix later

Debt nobody wrote down

Shortcuts pile up until every change is scary and slow. That is technical debt, and it grows quietly.

Technical debt, in plain words

Every shortcut taken today is a loan. You pay it back later with interest: bugs, slow changes and code nobody dares to touch. Getzilla makes the agent pay as it goes.

Four coworkers smiling around a laptop
Pull request #12Safe to merge
5/5checks passed
What you get

Sleep at night. Main still works in the morning.

Getzilla sorts out what the agent left behind. Every change gets tests that really ran, a short note on what and why, and a second pair of eyes. Anything not ready waits outside main with a clear to-do list.

  • Tests that actually ran, on the exact version you ship
  • Notes on what changed and why
  • A main branch you can deploy at any moment
See how it works →
How it works

Build first. Clean up second.

Getzilla does not slow down the fun part. Vibe-code the feature or the whole project first. Then Getzilla takes what was built and turns it into something you can trust.

Get it working, fast

Use your AI agent the way you like. Try ideas, throw them away, keep what works. Getzilla stays out of your way while you build.

  • No paperwork yet
  • No rules in your way
  • Just a working result

Your evening

you:      add a checkout with saved cards
agent:    done ✓
you:      make the button green
agent:    done ✓
you:      ship it?
getzilla: let me clean this up first
Why you can trust it

The agent cannot grade its own homework

The final check runs outside the agent’s reach: on a separate server, with tests the agent cannot see or edit. If a change is not proven, it does not get in, however confident the agent sounds.

Tests pass on the exact version being mergedGets in
“Trust me, it works” without proofStays out
Tests changed to pass instead of fixing the codeStays out
Nobody but the author has looked at itStays out
Get started

Try it on your project

Getzilla installs into an ordinary git repository. It shows you the plan first and changes nothing until you say so.

Open on GitHub
  1. 1Get Getzilla and check your machine
    git clone https://github.com/Dimkox/Getzilla.git
cd Getzilla
python3 scripts/getzilla_doctor.py --offer-install
  2. 2See what it would add to your project (read only)
    python3 scripts/install_into.py --plan /path/to/your/repo
  3. 3Or start a brand-new project with it
    python3 scripts/install_into.py --materialize-new /path/to/new-repo

Used adaptive-grok-build-pro before? Run the same --plan on your project. It keeps your own settings and lists every old file next to its Getzilla replacement.

Vibe-code tonight. Ship something you can maintain tomorrow.

Free and open source. Install it into your repository in a few minutes.

Try it on your project