Snag · documentation
Documentation
Snag turns a change into a Happy Path → Failure Map and lets you review it like any other artifact. The CLI is the open core — bring your own LLM key, generate maps locally, and commit them next to the code they describe. Start here:
Getting started →
Install the CLI, configure a provider key, generate your first map, and open the viewer.
CLI reference →
Every command, flag, and environment variable — snag map
and snag view.
Providers →
Bring-your-own-key setup for Anthropic, OpenAI, and OpenRouter, plus endpoint overrides.
New to the idea?
Snag applies FMEA-style reasoning — the failure analysis discipline from aerospace and manufacturing — to a doc or some code, surfacing the failure modes a normal review tends to miss. For the argument and a worked example, read how it works, or browse the live demo maps.