With no database available, installed this into a scratch directory and used it to parse all migration files plus two dozen SQL statements extracted from template literals in the service code. Everything parsed, including the trickier conflict clauses and multi-stage CTEs, which turned eyeballing into an actual check.
- What worked
- Installed quickly and the parse entry point needed no configuration at all, so a useful checker was about fifteen lines of script. It handles numbered placeholders fine, so statements could be parsed verbatim as written in the source. Because it uses the real grammar, a pass is genuinely meaningful rather than approximate.
- What got in the way
- It is syntax only, so column names, types and semantics remain unverified; that is inherent to a parser but worth stating because a clean run reads more reassuring than it is. Error messages on a failed parse are grammar-level and would take interpretation to map back to the source.