The Getzilla library

Guides

Practical methods for testing, reviewing and improving code you already have.

Working guide

AI code refactoring with evidence

Use AI for bounded code refactoring while preserving behaviour. Define invariants, review the diff, challenge generated tests and keep a reversible patch.

Working guide

How to reduce technical debt

Reduce technical debt through evidence, prioritisation and small verifiable changes. Use an outcome-based worksheet and keep accepted compromises explicit.

Working guide

Refactoring legacy code safely

Refactor legacy code with characterisation tests, a narrow seam and small reversible changes. Use a worksheet to preserve behaviour before changing structure.

Working guide

Technical debt assessment for a repository

Assess technical debt with evidence of change friction, defect risk and ownership. Use a practical matrix to turn repository findings into scoped backlog items.

Working guide

Vibe coding security checklist

Check identity, tenant access, secrets, inputs and dependencies in a vibe-coded app. Use a practical worksheet with evidence and clear pass conditions.

Working guide

From vibe-coded prototype to production

Assess a vibe-coded prototype before release: identity, data, failure handling, tests and rollback. Separate bounded repairs from missing product design.

Working guide

How to review AI-generated code

Review AI-generated code by checking its contract, trust boundaries, dependencies and tests. Use a practical diff review sheet tied to the final commit.

Working guide

C# unit testing with xUnit

Plan C# unit tests around exact outcomes, asynchronous results, parameterized boundaries, dependency seams, and the repository's existing test framework.

Working guide

How to add AI code review automation to CI

Plan AI code review automation around pull requests, safe permissions, actionable findings, and measured reviewer value before introducing blocking checks.

Working guide

How to assess AI-generated code quality

Evaluate AI-generated code for correctness, maintainability, integration fit, and test quality using concrete review questions and observable evidence.

Working guide

How to conduct a useful code review

Review code for behavior, design, tests, and maintainability with a practical sequence that turns findings into clear, actionable changes for the author.

Working guide

How to debug AI-generated code

Reproduce defects in AI-generated code, trace the failing boundary, and verify a focused fix with regression tests and useful diagnostic evidence.

Working guide

How to evaluate AI code review tools

Compare AI code review tools using your repository, known defects, data requirements, integration needs, and operating cost rather than unsupported rankings.

Working guide

Practical code refactoring techniques

Apply extract function, guard clauses, parameter objects, and responsibility separation with examples, prerequisites, and checks for behavior preservation.

Working guide

Run continuous test automation in CI

Plan continuous test automation with fast change checks, isolated data, clear failure artifacts, and separate stages for slower journeys.

Working guide

Security risks in AI-generated code

Identify security risks in AI-generated applications, from broken authorization to unsafe dependencies, and map each risk to evidence and controls.

Working guide

Unit testing vs. component testing

Compare unit and component tests by what they render, which dependencies remain real, and how they verify logic, interaction, and visible behavior.

Working guide

Unit testing vs. functional testing

Understand how unit and functional testing overlap, with practical examples of business requirements, isolated checks, and complete user outcomes.

Working guide

Unit testing vs. integration testing

Compare unit and integration testing with concrete examples of isolated rules, real dependencies, setup costs, and the failures each layer detects.

Working guide

What is AI-generated code?

Understand what AI-generated code is, where it helps, and how to review its dependencies, behavior, and ownership before using it in an application.

Working guide

What is a unit test?

Understand unit tests through inputs, expected outputs, dependency boundaries, and a practical example that separates logic from integration behavior.

Working guide

What is code refactoring?

Understand behavior-preserving code refactoring, when it helps, how it differs from rewriting, and what checks make structural improvements reviewable.

Working guide

What is legacy code?

Understand legacy code through change risk, missing knowledge, and unsupported dependencies, then decide what to preserve, test, refactor, or replace.

Working guide

What is legacy modernization?

Understand legacy modernization options, from targeted upgrades to incremental replacement, and connect each change to a concrete business constraint.

Working guide

What is software maintenance?

Understand software maintenance as changes to delivered software, with practical examples of corrective, adaptive, perfective, and preventive work.

Working guide

What is technical debt?

Understand technical debt as future change cost, distinguish it from defects and missing features, and use concrete evidence to decide when to address it.

Working guide

What is test automation?

Learn what test automation checks, where it fits in software delivery, and how to choose useful tests without replacing human exploration.

Working guide

Write Flutter unit tests for Dart logic

Test Flutter application logic with Dart test functions, explicit matchers, controlled async dependencies, and a clear boundary from widget and device tests.