Skip to main content
This page breaks down every component of a Greptile review so you know exactly what to expect and how to interpret the feedback.
New to Greptile? Start with the Quickstart to set up your first review.

​
The Review Process

When you open a PR, Greptile:
  1. Detects the PR and starts analyzing (you’ll see 👀)
  2. Builds context from your entire codebase, not just the diff
  3. Posts feedback as a PR summary + inline comments (you’ll see 👍)
Greptile analyzing

​
PR Summary

The PR summary is a top-level comment that gives you the big picture.

​
Components

​
Summary

Plain-language explanation of what the PR does, who it affects, and why. Includes major improvements and any issues found.
PR Summary

​
Confidence Score

A 0-5 rating that tells you at a glance whether the PR is ready to merge. Greptile calculates this based on the severity and quantity of issues found, the complexity of changes, and how well the code aligns with your codebase patterns.
Scores are contextual. A 3/5 on a payments feature is more serious than a 3/5 on an internal script.

​
Files Changed & Issues

File-by-file breakdown showing what changed and issues found per file.
Files Changed

​
Diagrams

Greptile automatically generates a diagram to visualize the changes in your PR. The diagram type is selected based on what changed: For minimal or trivial changes, no diagram is generated. Example (sequence diagram for an API flow):
You can request a specific diagram type by replying to the review or tagging @greptileai — for example, “generate a class diagram for this PR”.
Configure which components appear in your dashboard:
PR summary settings
The footer of the PR summary shows review metadata and actions:
Review footer with counter, commit link, and re-trigger button

​
Inline Comments

Greptile posts comments directly on specific lines where it finds issues.
Inline Comment

​
Severity Badges

Each inline comment includes a severity badge indicating its priority:
Inline comment with P2 severity badge

​
Comment Types

Comment types are controlled with the commentTypes field in .greptile/config.json.
.greptile/config.json
All types are enabled by default. To focus reviews, list only the types you want Greptile to leave. See Controlling Nitpickiness for examples.

​
Suggested Fixes

Most comments include a code suggestion you can apply:
With MCP, apply fixes directly from your IDE without copy-pasting.

​
Troubleshooting

Check:
  • Repository enabled in dashboard
  • Not a draft PR (skipped by default)
  • Branch not excluded by filters
  • Indexing complete (first time: ~1-2 hours)
Fix: Comment @greptileai to trigger manually

​
What’s Next

Now that you understand what a review looks like, learn how to interact with Greptile:

Developer Essentials

Reactions, follow-ups, training, and daily workflows

Control Nitpickiness

Control what Greptile flags

Auto-fix in IDE

Apply fixes without leaving your editor

Custom Standards

Enforce your team’s rules