review

A pre-landing pull request review analyzes your git diff against the base branch to identify SQL injection risks, race conditions, and LLM trust boundary violations before code merge. This two-pass process catches critical bugs early to prevent production incidents.

A two-pass code review process first flags critical issues like SQL safety, shell injection, and race conditions, then catches informational issues like async/sync mixing, dead code, and type coercion. This methodical approach ensures both critical and minor structural problems are caught before landing changes.

To catch LLM trust boundary violations in a pull request, analyze the git diff to identify where untrusted inputs cross into LLM processing logic. Pre-landing review heuristics distinguish these security findings from auto-fixable mechanical issues, escalating them for human judgment before merge.

Yes, the pre-landing review workflow fetches and triages Greptile bot comments on GitHub pull requests, classifying each comment as a valid issue, a false positive, or already fixed. This integration streamlines automated bot feedback into your manual review process.

Yes, you can automatically fix mechanical issues like N+1 queries, magic numbers, and dead code found during a pull request review. The fix-first workflow auto-resolves these structural problems while escalating complex security and design decisions to the user.

Automated security detection in git diff parsing cannot resolve judgment-based security findings or design decisions, requiring human escalation. It is limited to identifying known patterns like SQL injection and race conditions, meaning novel or context-dependent vulnerabilities may be missed.