Anatomy of a Review

Fresh

Understand every component of a Greptile code review: PR summaries, confidence scores, inline comments, suggested fixes, and diagrams explained.

This page breaks down every component of a Greptile review so you know exactly what to expect and how to interpret the feedback.

Note

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 👍)

Analyzing

!Greptile analyzing

Complete

!Greptile complete

Status	Emoji	Typical Duration
Analyzing	👀	~3 minutes
Complete	👍	-
Failed	😕	Tag @greptileai to retry

---

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

Summary with major improvements and issues

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.

Score	Meaning	Action
5/5	Production ready	Merge
4/5	Minor polish needed	Merge after small fixes
3/5	Implementation issues	Address feedback first
2/5	Significant bugs	Needs rework
0-1/5	Critical problems	Major rethink needed

Note

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

File analysis with issues

Diagrams

Greptile automatically generates a diagram to visualize the changes in your PR. The diagram type is selected based on what changed:

Type	When Generated
Sequence	Multi-service interactions, API flows
Entity Relation	Schema or data model changes
Class	Class hierarchy changes
Flow	Control flow or business logic changes

For minimal or trivial changes, no diagram is generated.

Example (sequence diagram for an API flow):

sequenceDiagram
    participant Client
    participant API
    participant Database

    Client->>API: Request
    API->>Database: Query
    Database-->>API: Result
    API-->>Client: Response

Tip

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

PR Summary Settings

Review Footer

The footer of the PR summary shows review metadata and actions:

!Review footer with counter, commit link, and re-trigger button

Review footer

Element	Description
Review counter	Shows how many times Greptile has reviewed this PR (e.g. "Reviews (2)")
Last reviewed commit	Links to the most recent commit that was reviewed, with a longer commit message preview
Re-trigger Greptile	Click to manually re-run a review on the current PR state

---

Inline Comments

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

!Inline Comment

Inline Comment with Suggested Fix

Severity Badges

Each inline comment includes a severity badge indicating its priority:

!Inline comment with P2 severity badge

Severity badge on an inline comment

Badge	Severity	Description
P0	Critical	Must fix before merging, security vulnerabilities, data loss, crashes
P1	High	Should fix, bugs, incorrect behavior, edge cases
P2	Medium	Consider fixing, code quality, maintainability, best practices

Comment Types

Type	What it catches	Examples
Logic	Bugs, incorrect behavior, edge cases	Null pointer, race condition, wrong return value
Syntax	Code that won't compile/run	Missing import, typo, invalid syntax
Style	Code quality, best practices	Naming conventions, dead code, complexity

Control which types appear in Code Review Settings under What should Greptile comment on?, or via greptile.json.

Suggested Fixes

Most comments include a code suggestion you can apply:

- const data = fetchData()
+ const data = await fetchData()

With MCP, apply fixes directly from your IDE without copy-pasting.

---

Troubleshooting

Review didn't appear

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

Fine-tune what Greptile flags

Auto-fix in IDE

Apply fixes without leaving your editor

Custom Standards

Enforce your team's rules

Source

Mirrored from the official Greptile documentation. Self-contained reference copy.