AI code review
heyGRC alongside Greptile
Greptile is built to review a change with context from across your repository, to catch system-wide bugs and inconsistencies. heygrc is built to review the same pull request against the compliance frameworks you selected and to cite the control a change touches. Whole-repo context about behaviour and framework context about obligations are different jobs, so the tools sit side by side. (For a fuller comparison with a worked example, see heygrc vs Greptile.)
What Greptile focuses on
- Indexing the repository so review comments use cross-file context.
- Flagging likely bugs and inconsistencies that only show up with that context.
- Commenting on the pull request with what it finds.
What heygrc adds alongside it
- Whether a change drops encryption or a TLS floor on a path that carries personal or sensitive data, the kind of weakening a security-of-processing duty cares about.ISO 27001 A.8.24 in code→
- Whether a delete path stops short of a secondary store so erasure cannot complete, even when the primary delete is correct.GDPR right to erasure in code→
- The compliance reading of a change, mapped to the framework you are audited on, as the specific control it touches.
Use them together
Let Greptile use whole-repo context to catch system-wide bugs; let heygrc tell you when a change touches a compliance control.