Related question, does the chapter view help for security review? Code review catches "is this well written", but security review is more like "did the author forget the auth check on this new endpoint, or remove a tenant filter by accident". Those aren't really visible as a chapter since the problem is what's not in the diff. Curious if the authors have thought about that use case or if it's a separate tool entirely.
Good question, we're more focused on the first aspect you mentioned of "does the code you wrote make sense on a high level" rather than "did you miss something" - I think tools like Greptile and Codex are coming out with new security review features that are more suited towards that use case