Skip to main content
Use Greptile MCP tools to fetch unaddressed comments and apply fixes directly from your IDE.
Prerequisite: Configure MCP in your IDE before following these workflows.
Using Claude Code? Agent skills automate the entire auto-fix loop for you. Run /check-pr to fix all review comments on a PR, or /greploop to iterate until Greptile gives a 5/5 confidence score.

​
Your First Auto-Fix

1

Fetch unaddressed comments

Ask your AI assistant:
The assistant calls list_merge_request_comments with addressed: false.
Unaddressed PR comments
2

Review the response

You’ll see comments with their details including file path, issue type, and whether a fix is available.
3

Apply fixes

For comments with hasSuggestion: true:
The assistant applies the suggestedCode to your file.
Code changes for review
4

Accept changes

Review the changes, then click Keep All to apply them to your codebase.
5

Commit changes

After applying fixes, commit your changes. Greptile automatically marks comments as addressed when the file is modified.

​
Understanding Comment Fields

When you fetch comments, each one includes these key fields:

​
How Comments Get “Addressed”

A comment becomes addressed when there’s a commit after the comment that modifies the relevant file:
Check progress via reviewAnalysis.reviewCompleteness (e.g., “2/5 Greptile comments addressed”).

​
Common Prompts

The assistant filters for hasSuggestion: true.
Searches comment bodies for style-related keywords.
Uses get_merge_request and checks reviewAnalysis.reviewCompleteness.
Filters results by filePath.
Checks the linkedMemory field for the associated custom context.

​
Next Steps

Agent Skills

Automate the full auto-fix loop with /check-pr and /greploop

Custom Context

Learn how linkedMemory connects comments to your patterns

Tools Reference

Complete field documentation for all responses