Skip to main content

Documentation Index

Fetch the complete documentation index at: https://www.greptile.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

The Greptile plugin for Claude Code gives you direct access to your code reviews from the terminal. Fetch PR comments, apply fixes, and search review feedback without leaving your workflow.
Prerequisite: Create a Greptile account at app.greptile.com and connect your repositories.

​
Installation

1

Get Your API Key

Go to app.greptile.com/settings/organization/api (Settings > Organization > API Keys) and copy your API key.
2

Set Environment Variable

Add your API key to your shell configuration:
export GREPTILE_API_KEY="your-api-key"
3

Open Claude Code

Launch Claude Code in your terminal:
claude
Claude Code welcome screen
4

Open Plugin Browser

Type /plugins to open the plugin discovery interface.
Claude Code plugin browser
5

Search for Greptile

Type greptile to search for the plugin.
Searching for Greptile plugin
6

Install

Select the Greptile plugin and choose your installation scope:
  • User scope — Available in all your Claude Code sessions
  • Project scope — Available to all collaborators on this repository
  • Local scope — Available only in this repository for you
Greptile plugin installation options

​
What You Can Do

Once installed, ask Claude Code to work with your Greptile reviews using natural language.

​
Fix All Comments on a PR

Show me all Greptile comments on my open PR and fix them
Claude will fetch unaddressed comments, analyze the suggested fixes, and apply them directly to your code.
Claude Code applying a fix from a Greptile comment

​
Analyze Security Concerns

Get the full review analysis for PR #2 and explain the security concerns
Claude fetches the complete review and breaks down any security-related feedback.
Claude Code showing security analysis from Greptile review

​
Summarize Blocking Issues

Find all my open PRs with unresolved Greptile comments and summarize what's blocking them
Get a quick overview of what needs attention across all your open pull requests.
Claude Code summarizing blocking issues across PRs

​
Example Prompts

​
Pull Requests & Reviews

TaskPrompt
List your open PRs”Show me all my open pull requests”
Filter by author”List PRs authored by @johndoe”
Get PR details”Get the full details for PR #42 including review status”
Check review status”Has PR #15 been reviewed? What’s still unaddressed?”
Trigger a review”Run a Greptile review on PR #8”

​
Working with Comments

TaskPrompt
List unaddressed comments”What Greptile comments are still unaddressed on PR #5?”
Fix a specific comment”Fix the null check issue Greptile found in auth.ts”
Fix all comments”Show me all unaddressed comments and fix them one by one”
Search across repos”Search for comments mentioning ‘SQL injection’ across all my PRs”
Find patterns”What are the most common issues Greptile has flagged this month?”

​
Custom Context

TaskPrompt
List coding standards”What custom context rules does my org have?”
Search for a pattern”Do we have any rules about error handling?”
Create a new rule”Create a custom context rule: always use parameterized queries for database access”

​
Available Tools

The plugin uses Greptile’s MCP server, giving you access to 11 tools:
  • list_pull_requests — List PRs with filters (author, state, branch)
  • get_merge_request — Get full PR details including review analysis
  • list_merge_request_comments — Get all comments on a PR
View full parameters →
  • list_code_reviews — List reviews with status filters
  • get_code_review — Get detailed review information
  • trigger_code_review — Start a new review on a PR
View full parameters →
  • search_greptile_comments — Search all Greptile comments across repos
View full parameters →
  • list_custom_context — List org coding patterns
  • get_custom_context — Get pattern details
  • search_custom_context — Search patterns by content
  • create_custom_context — Create new patterns
View full parameters →

​
Learn More

​
Troubleshooting

Make sure you’re running Claude Code v2.1 or later. Check your version and update:
claude --version
claude update
Verify your API key is set correctly:
echo $GREPTILE_API_KEY
If empty, add it to your shell config (~/.zshrc or ~/.bashrc) and restart your terminal.
Check that:
  • Your repositories are connected in app.greptile.com
  • You have open PRs with Greptile reviews
  • Your API key has access to those repositories

​
Next Steps

Agent Skills

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

Auto-Fix Workflow

Manual patterns for resolving review comments

Custom Context

Add your team’s coding standards for better reviews