Skip to main content
Agent skills automate the full auto-fix workflow in Claude Code. 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.
Prerequisites:

Install

Install all three skills with the skills CLI (recommended):
To install into a single project instead of globally, run this from the project root:

Alternative: git clone

Clone the skills into your Claude Code skills directory, then symlink each skill into place. See the Claude Code skills docs for more on how skill discovery works.

check-pr

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

Usage

Or with a specific PR number:
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:
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 and summarizes the findings. Use it to get Greptile feedback before opening a PR.

Usage

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

Or with a specific PR number:

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:
If the loop hits the iteration limit:

Next Steps

Auto-Fix Workflow

Manual auto-fix patterns using MCP tools

Claude Code Setup

Set up the Greptile MCP server for Claude Code