Run the existing `greploop` workflow with the `@greptile-apps` trigger when the usual trigger cannot handle a large pull request. This entrypoint depends on the separate `greploop` skill and adds no workflow of its own.
Run the greploop workflow with the @greptile-apps trigger when the normal trigger refuses a large PR. Requires the greploop skill installed alongside this entrypoint.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
This is a compatibility entrypoint for /greploop --trigger @greptile-apps.
Read the installed greploop skill and follow its workflow with that trigger.
Preserve the user's target, iteration cap, task scope, and existing authorization.
In this collection the shared workflow is greploop.
If installed separately, locate greploop in the environment's skill catalog.
If it is missing, report the dependency and provide the paired installation
command below. Do not invent a second workflow or install dependencies without
an installation request.
cp -r greploop greploop-apps ~/.claude/skills/
All polling, freshness checks, platform references, and stopping conditions
belong to greploop. This entrypoint contains no separate implementation.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Capture two web pages or image files for a visual comparison. Choose a page element with a CSS selector, set a mobile, tablet, or custom viewport, and create a Markdown comparison for PRs when needed.
Use this guide to decide when repeated operational code should become a shared service, while keeping product rules in the workflow actions that own them. It provides practical design principles and a gradual migration checklist to preserve existing boundaries and behavior.
Verify changed behavior with evidence suited to the task: a live screen recording for interactive UI flows, scripted captures for headless checks, or measured outputs for non-UI changes. Create a results report and send the evidence to the requested destination when authorized.
Review Greptile feedback on a pull request, merge request, or shelved changelist, then make scoped fixes and request fresh reviews within a set cycle limit. Track actionable findings and report the current score, checks, and any work left unresolved.
Prepare an isolated Git worktree and branch for each feature, fix, or documentation task. Check for an existing assignment and overlapping pull requests first, so edits stay scoped to the right work and do not build on another task’s changes.
Edit text for people to remove common AI writing patterns while keeping its meaning and intended tone. The skill checks for vague claims, formulaic phrasing, filler, and stiff language, then revises the text with more specific wording and varied rhythm.