Snag · FMEA for pull requests
The failure modes a code review would miss.
Snag turns a change into a Happy Path → Failure Map: the blue spine is what should happen; everything branching off is how it can silently go wrong — the structurally-missed failure modes line-by-line review tends to skip.
Open-core CLI — bring your own LLM key; nothing is proxied through a Snag service. The maps below are live — open any to explore it.
How it works
The short version is three steps — or read the FMEA argument and a worked example.
Point it at a change
snag map <file>
turns a doc, a code file, or a named behavior into a map.
Explore the failure map
snag view
opens it as an interactive Happy Path → Failure Map — the same viewer the maps below use.
Versioned with the change
Each map is JSON committed to git, so the analysis lives and diffs next to the code it describes.
Engineering maps
Map a change before you ship it and the subtle failure modes — the edge cases easy to miss in an automated or human review, that only bite in production — surface while they're still cheap to fix.
Business-process maps
The same maps work on processes, not just code. Product: rank failure modes by impact to decide what to harden or build next. Sales: surface the high-cost problems in a prospect's process that your solution can point at.
What's next
The CLI is the open core. A collaborative layer is on the way:
Something else you'd want snag to do? Request a feature →