Greploop
Address Greptile feedback on a PR, MR, or shelved changelist through bounded review and...
Install
npx skills add michaelshimeles/rstack --skill greploop -g -a claude-code -y- Repository
- michaelshimeles/rstack1.4k
- Category
- Git and review
- Updated
- 9d ago
- License
- MIT
- Context cost
- Lightabout 852 tokens
- Runs scripts
- Yes, review before use
What it does
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.
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 @greptileby default, or@greptile-appsfor the alternate route. Use the alternate when the normal trigger reports too many changed files.--vcs github|gitlab|perforcewhen 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: the bundled helper tracks each trigger and waits for a scored review tied to the current commit.
- GitLab: use notes and resolvable discussions; CI pipeline activity alone does not identify a Greptile review.
- Perforce: use the configured Swarm or site adapter.
