comprehension-gate

Paste the diff or PR description into the comprehension gate workflow, optionally adding system context like a module manifest or dependency description. It returns a findings table ordered by severity, a blast radius map, and questions that must be answered before merging.

It checks seven dimensions: credential and secret exposure, cross-service side effects, blast radius, state and persistence changes, token and session TTLs, implicit assumptions, and whether the change is understandable in isolation. It explicitly does not review style, naming, or test coverage.

Yes, a description of the change works, but the review will note where the actual code would enable more specific analysis. Providing the real diff plus system context such as dependency maps produces the most precise blast radius assessment.

Do not use it as a substitute for linters, CI test suites, or style checks, since it deliberately ignores syntax and coverage. It also cannot assess blast radius without system context, so it will explicitly state when dependency information is missing.

CLEAR means intent matches behavior and blast radius is bounded. REVIEW REQUIRED means specific listed questions need answers before shipping. HOLD means the change shows signs the author may not understand system-level implications and needs senior engineer review of Critical findings.