# Greploop

Address Greptile feedback on a PR, MR, or shelved changelist through bounded review and...

- Repository: https://github.com/michaelshimeles/rstack (1423 stars)
- Category: Git and review
- License: MIT
- Last updated: 2026-10-26
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add michaelshimeles/rstack --skill greploop -g -a claude-code -y`
Codex: `npx skills add michaelshimeles/rstack --skill greploop -g -a codex -y`
Cursor: `npx skills add michaelshimeles/rstack --skill greploop -g -a cursor -y`
Gemini CLI: `npx skills add michaelshimeles/rstack --skill greploop -g -a gemini-cli -y`

## Description

Address Greptile feedback on a PR, MR, or shelved changelist through bounded review and fix cycles. Use when the task includes a Greptile review loop. Supports the alternate @greptile-apps trigger for large PRs.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Greploop

Improve the requested change using Greptile feedback. Success means a fresh
5/5 review of the current revision with no unresolved actionable Greptile
findings. The bot's score complements the project's checks and your judgment.

## Inputs

- PR, MR, or changelist number. Infer it from the current task when omitted.
- `--max-iterations N`, a positive integer, defaults to 10 review cycles.
- `--trigger @greptile` by default, or `@greptile-apps` for the alternate route.
  Use the alternate when the normal trigger reports too many changed files.
- `--vcs github|gitlab|perforce` when repository context is ambiguous.

Apply the user's existing authorization and task scope. A read-only review
request does not authorize code edits or posting comments. Keep your own task's
worktree and branch; do not switch another task's checkout to the PR branch.

## Choose the platform

Use the repository and session context, not an installed executable alone.
Read only the relevant reference:

- [GitHub](references/github.md): the bundled helper tracks each trigger and
  waits for a scored review tied to the current commit.
- [GitLab](references/gitlab-api.md): use notes and resolvable discussions;
  CI pipeline activity alone does not identify a Greptile review.
- [Perforce](references/perforce.md): use the configured Swarm or site adapter.

## Review cycle

The rest: https://github.com/michaelshimeles/rstack/blob/HEAD/greploop/SKILL.md