> ## 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.

# Agent Skills

> Automated Claude Code skills for fixing PR review comments and iterating to a perfect Greptile score.

Agent skills automate the full auto-fix workflow in [Claude Code](https://claude.ai/download). Instead of manually prompting your assistant to fetch comments and apply fixes, invoke a skill and let it handle the entire loop.

All three skills (`check-pr`, `cli-review`, and `greploop`) are open source and available at [github.com/greptileai/skills](https://github.com/greptileai/skills).

> [!NOTE]
>
> **Prerequisites:**
>
> * [Claude Code](https://claude.ai/download) installed
> * `git` and `gh` (GitHub CLI) installed and authenticated
> * [Greptile installed](https://app.greptile.com/signup) on your repository
> * [Greptile MCP server configured](https://www.greptile.com/docs/mcp/setup.md) in Claude Code

## Install

Install all three skills with the [skills CLI](https://skills.sh) (recommended):

```bash theme={}
npx skills add greptileai/skills -g
```

To install into a single project instead of globally, run this from the project root:

```bash theme={}
npx skills add greptileai/skills
```

### Alternative: git clone

Clone the skills into your Claude Code skills directory, then symlink each skill into place. See the [Claude Code skills docs](https://docs.anthropic.com/en/docs/claude-code/skills) for more on how skill discovery works.

```bash theme={}
git clone https://github.com/greptileai/skills.git ~/.claude/skills/greptile
cd ~/.claude/skills
ln -sfn greptile/skills/check-pr check-pr
ln -sfn greptile/skills/cli-review cli-review
ln -sfn greptile/skills/greploop greploop
```

***

## check-pr

Checks a pull request for unresolved review comments, failing status checks, and incomplete descriptions — then fixes and resolves them.

### Usage

```text theme={}
/check-pr
```

Or with a specific PR number:

```text theme={}
/check-pr 42
```

If no PR number is given, the skill auto-detects the PR for your current branch.

### What It Does

**1. Waits for pending checks**

Polls until all CI and review bot checks (Greptile, linters, etc.) reach a terminal state. This ensures all comments are available before analysis.

**2. Analyzes the PR**

Evaluates four areas:

* **Status checks** — Are CI checks passing or failing?
* **PR description** — Is it complete? Any TODOs or placeholders?
* **Review comments** — Inline comments from Greptile, linters, and human reviewers
* **General comments** — Discussion threads and bot notifications

**3. Categorizes issues**

Each issue is classified as:

| Category | Meaning |
| - | - |
| **Actionable** | Code changes, test improvements, or fixes needed |
| **Informational** | Verification notes, questions, or FYIs |
| **Already addressed** | Resolved by subsequent commits |

**4. Fixes and resolves**

If there are actionable items, the skill makes the fixes, commits, pushes, and resolves the corresponding review threads.

***

## cli-review

Runs a Greptile review from your local checkout with the [Greptile CLI](https://www.greptile.com/cli) and summarizes the findings. Use it to get Greptile feedback before opening a PR.

### Usage

```text theme={}
/cli-review
```

Run it from inside a git repository. The skill reviews the current local branch.

`/cli-review` only needs the Greptile CLI; it doesn't use `gh` or the Greptile MCP server.

Commit your changes first. The review covers committed changes on the current branch, not uncommitted edits.

### What It Does

**1. Checks for the Greptile CLI**

Confirms `greptile` is installed. If it's missing, the skill asks before installing it with `npm i -g greptile`.

**2. Ensures authentication**

Runs `greptile whoami` and prompts you through `greptile login` if needed.

**3. Runs the review**

Runs `greptile review --json`, falling back to `greptile review --agent` if JSON output isn't supported.

**4. Summarizes findings**

Reports the review status, number of findings, highest-severity issues first, and the files that need edits.

***

## greploop

Iteratively improves a PR until Greptile gives it a 5/5 confidence score with zero unresolved comments. Triggers a Greptile review, fixes all actionable comments, pushes, re-triggers, and repeats.

### Usage

```text theme={}
/greploop
```

Or with a specific PR number:

```text theme={}
/greploop 42
```

### What It Does

**1. Triggers a Greptile review**

Pushes the latest changes and waits for the Greptile review check to complete.

**2. Parses review results**

Reads the confidence score (e.g. `3/5`) and fetches all unresolved inline comments from Greptile.

**3. Fixes actionable comments**

For each unresolved comment, reads the file in context, determines if a code change is needed, and applies the fix. Informational comments and false positives are noted and resolved.

**4. Commits, pushes, and loops**

Commits the fixes, pushes, and goes back to step 1. The loop runs up to **5 iterations** to avoid runaway cycles.

**5. Exits when clean**

Stops when Greptile returns **5/5 confidence** with **zero unresolved comments**, or after the max iterations.

### Output

On success:

```
Greploop complete.
  Iterations:    2
  Confidence:    5/5
  Resolved:      7 comments
  Remaining:     0
```

If the loop hits the iteration limit:

```
Greploop stopped after 5 iterations.
  Confidence:    4/5
  Resolved:      12 comments
  Remaining:     2

Remaining issues:
  - src/auth.ts:45 — "Consider rate limiting this endpoint"
  - src/db.ts:112 — "Missing index on user_id column"
```

***

## Next Steps

> **[Auto-Fix Workflow](https://www.greptile.com/docs/mcp/auto-fix.md)**
>
> Manual auto-fix patterns using MCP tools

> **[Claude Code Setup](https://www.greptile.com/docs/mcp/setup.md#claude-code-cli)**
>
> Set up the Greptile MCP server for Claude Code


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.