Greptile skills
Three skills work through Greptile review comments on a pull request, fix them and re-run the review until none are left open
- 431 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- `greploop` pushes commits to the branch in a loop and resolves PR discussion threads, including ones it marks as false positives
- The skills call `gh`, `glab`, `p4` and `git` with your credentials and change repository state
- The plugin sends code and comments to Greptile servers, and sign-in goes through OAuth
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/greptile-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- `greploop` pushes commits to the branch in a loop and resolves PR discussion threads, including ones it marks as false positives
- The skills call `gh`, `glab`, `p4` and `git` with your credentials and change repository state
- The plugin sends code and comments to Greptile servers, and sign-in goes through OAuth
This is third-party code. Review the repository files before installing.
What it does
Greptile is a code review service that comments on pull requests. This repository gives an agent three commands for working with those comments. `check-pr` inspects a PR, merge request or Perforce shelved changelist: it looks for unresolved comments, failing checks and an empty description, waits for pending checks and sorts findings into actionable and informational. `greploop` runs a loop: it triggers a Greptile review, fixes the comments, pushes and repeats until the score reaches 5 out of 5 with no open comments. `cli-review` runs the Greptile CLI on a local branch before any PR exists and summarizes the findings. The skills detect the platform themselves: a `.p4config` file or `P4PORT` and `P4CLIENT` variables mean Perforce, and the remote URL separates GitLab from GitHub. A matching client has to be installed: `gh`, `glab`, `p4` or `greptile`. The repository also holds a `greptile` plugin for Claude Code and Codex that brings an MCP server and the CLI, with `login` and `review` skills.
Who it is for. Teams whose pull requests Greptile reviews and who want an agent to take over the routine: reading comments, fixing findings and re-reviewing.
Good fit when
- A PR has dozens of Greptile comments and they get handled in one batch
- Before merging you want green checks, a filled-in description and every discussion thread closed
- A branch is not yet a PR but you want Greptile to look at it from the terminal
- The repository lives in GitLab or Perforce and reviews still go through Greptile
- The `greptile` plugin is wanted to read finished reviews and search them from the agent
Not a fit when
- Reviews come from a tool other than Greptile: `greploop` waits for Greptile's own 5 out of 5
- Pushing to the branch automatically is not acceptable: the `greploop` cycle pushes changes itself
- The repository has no Greptile connected: without its score the loop never finishes
- You have no access to the repository through `gh` or `glab` under your account
Example request
Check my current pull request: show unresolved Greptile comments and failing checks, fix what concerns the code and list the restLimitations
The skills work only alongside Greptile: without the service installed on the repository, `greploop` has no score to wait for. An authenticated client for the platform is required (`gh auth login`, `glab auth login`, `P4PORT`, `P4USER` and `P4CLIENT` settings, or `greptile login`). For self-hosted GitLab without "gitlab" in the host name, pass `--vcs gitlab`; for Perforce, pass `--vcs perforce` if detection fails. `greploop` pushes commits and resolves discussion threads without you in the loop, while `cli-review` asks before installing the CLI. The plugin signs in through OAuth at auth.greptile.com, and the CLI keeps its tokens in `~/.greptile/auth.json` separate from the MCP tokens.
How to disable. Delete the `check-pr`, `greploop` and `cli-review` skills from your agent's skills folder. If you set up symlinks under `~/.claude/skills`, remove them together with the `~/.claude/skills/greptile` clone. The plugin is disabled through `/plugin`; CLI tokens sit in `~/.greptile/auth.json`.
FAQ
How do I install the Greptile skills in Claude Code?
Run `npx skills add greptileai/skills -g` and all three skills install globally; without `-g` they install into the current project. Invoke them by name: `/check-pr 123`, `/cli-review` or `/greploop`.
How is check-pr different from greploop?
`check-pr` makes one pass: it collects comments, check status and the description, and optionally fixes what it finds. `greploop` repeats the Greptile review and the fixes in a cycle until the score is 5 out of 5 with no open comments.
Does it work with GitLab and Perforce?
Yes. GitLab needs `glab`, Perforce needs `p4` with `P4PORT`, `P4USER` and `P4CLIENT` set. If the GitLab host name has no "gitlab" in it, add `--vcs gitlab`.
Can I run a review before opening a pull request?
Yes, with the `cli-review` skill. It runs the Greptile CLI in the current repository and summarizes the findings. If the CLI is missing, the skill asks permission before installing it.
What does the greptile plugin add?
The MCP server `https://api.greptile.com/mcp` and the CLI. Through the server the agent reads finished reviews, searches comments and the knowledge base, and triggers PR reviews. Install the plugin with `/plugin marketplace add greptileai/skills` and `/plugin install greptile@greptile-plugin`.
Discussion
No questions or reviews yet.
Related
SkillsTwo skills: a pull request review where two models argue, and a helper that works through review comments round by round
kyy-logs code-review-skill
code-review-skill
A code review skill with four independent probes, evidence-backed findings and a merge gate derived from JSON
A code-review CLI and plugin for agents: reads a git diff and writes line-level comments with context
A CLI and three skills that work through review-bot comments on a PR: assess findings, fix code, reply and wait for checks
A skill that draws every pull request as an architecture and data-flow diagram right in the PR description, to speed up review
Local review of agent changes before commit: the agent itself reads line comments and replies to them through MCP.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Greptile skills (this card) | yes | 431 | |
| code-review-skill | no | 2,191 | a general code review checklist for an agent; Greptile skills work through Greptile service comments and run the fix loop |
| Claude Code Security Reviewer | no | 6,719 | a GitHub Action for vulnerabilities in PRs; Greptile skills run on the developer's machine and fix findings |
README in short
The page opens with a table of the three skills and a table of clients per platform. Next come two install routes (the skills CLI and a clone with symlinks), usage examples and a paragraph on the Claude Code and Codex plugin that links to its own README.
README badge
Original SKILL.md
---
name: check-pr
description: >
Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist)
for unresolved review comments, failing status checks, and incomplete PR descriptions. Waits for
pending checks to complete, categorizes issues as actionable or informational, and optionally fixes
and resolves them. Use when the user wants to check a PR/MR/CL, address review feedback, or prepare
a change for submission.
license: MIT
compatibility: Requires git and gh (GitHub CLI), glab (GitLab CLI), or p4 (Perforce CLI) installed and authenticated.
metadata:
author: greptileai
version: "1.3"
allowed-tools: Bash(gh:*) Bash(glab:*) Bash(git:*) Bash(p4:*)
---
# Check PR
Analyze a pull request (GitHub), merge request (GitLab), or shelved changelist (Perforce) for review comments, status checks, and description completeness, then help address any issues found.
## Inputs
- **PR/MR/CL number** (optional): If not provided, detect the PR/MR for the current branch, or the default pending changelist for p4.
## Instructions
### 0. Detect platform
First check if the user is working in a Perforce depot by looking for a `.p4config` file or `P4CLIENT`/`P4PORT` environment variables:
```bash
# Check for Perforce environment
if p4 info >/dev/null 2>&1; then
VCS="perforce"
else
# Fall back to git remote detection
REMOTE_URL=$(git remote get-url origin)
if echo "$REMOTE_URL" | grep -qi "gitlab"; then
VCS="gitlab"
else
VCS="github"
fi
fi
```
For self-hosted GitLab instances whose hostname doesn't contain "gitlab", the user can override by passing `--vcs gitlab` as an input. For Perforce, the user can override by passing `--vcs perforce`.
### 1. Identify the PR/MR/CL
If a number was provided, use it. Otherwise, detect it: