Home

l0-git Wiki

Checks a repository for the things that are simply true or false about it: a missing licence, a tracked .env, a FROM node:latest, an unresolved merge marker. 35 gates, one Go binary, and one store that your shell, your editor and your coding agent all read from.

The documentation site is the reference: getting started, the gate reference with a page per gate, the CLI, configuration, MCP and the extension. This wiki covers what happens when you point it at a repository that already exists.

Pages

• Adopting it: the first run, what to fix, what to silence, and the three ways to silence something
• When a gate is wrong: determinism is about bytes, not about meaning. This repository's own config is the worked example
• One store, three front ends: the property that makes it different, and what follows from it
• FAQ

The rule that decides what is a gate

A gate fires if and only if the violation can be expressed as a binary, mathematically unambiguous condition over the file system, the git index, or a parse tree.

That constraint is the product. It buys reproducibility: the same tree gives the same findings on any machine, with no model, no network and no threshold to tune.

It explicitly does not buy being right about intent, and the README says so rather than leaving you to find out. Anything needing genuine context understanding is deliberately not a gate: it goes down the remediation path, where being wrong costs a suggestion instead of a red build.

Three commands

lgit check .                              # run every gate, persist findings
lgit list -project=$PWD -severity=error   # just what matters now
lgit fix <id>                             # what to do about one of them

Everything prints JSON except lgit fix, which prints for humans unless you pass --json. For eight gates, fix hands you the exact commands rather than advice.