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.
Isolate repository edits in a Git worktree before starting a feature, fix, or documentation change. Preserve a worktree already assigned to the same task. Read-only reviews and investigations do not need a new worktree.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Each editing task gets its own worktree and branch, created from the latest
origin/main unless the user specifies a different base. Read-only work can
use the existing checkout. Never build on main or reuse another task's work.
Inspect git worktree list, git status --short, the current branch, and the
session's task assignment. If the environment already created a worktree for
this task, keep its path and branch and skip steps 3 and 4. In step 5, use the
actual assigned path. Do not infer isolation from the editor name or a branch
prefix alone. Otherwise follow all steps.
Sync: git fetch origin.
Scope check: run gh pr list and skim the open PRs' changed files
(gh pr diff <n> --name-only). For shared files, read the overlapping
diffs. Independent edits may proceed in your own worktree. Ask for direction
only when the changes conflict in behavior, require another task's unfinished
work, or ownership is unclear. Check shared checkouts for uncommitted work
without changing it. On another hosting platform, use its equivalent PR/MR
tools; if unavailable, report the scope-check limitation and still isolate.
Name the task: lowercase-with-hyphens plus a short unique suffix,
e.g. user-auth-0816a. If git worktree add fails because the name
exists, pick a different name — never force or reuse.
Create the worktree from the repo root:
git worktree add <worktrees-dir>/<task-name> \
-b <branch-prefix>/<task-name> origin/main
Use a directory outside the checkout, or a gitignored directory inside
it, so worktrees cannot be committed by accident. Use a
consistent branch prefix (e.g. agent/). Follow the repo's conventions
if it defines them.
Enter and verify:
cd <worktrees-dir>/<task-name>
git branch --show-current # must print your new branch, not main
Confirm the required runtime version. Install dependencies inside the worktree when needed for the task's checks. Documentation-only work does not require installing an unrelated application toolchain.
Worktrees do not isolate dev-server ports or shared databases.
Tracked dependency lockfiles are separate in each worktree. Confirm a port answers
your process (lsof -i :<port>) before trusting what it serves, and
resolve lockfile conflicts by regenerating, never by hand-merging.
Keep the worktree until the PR is merged or closed. Cleanup after merge:
git worktree remove <worktrees-dir>/<task-name>
git branch -D <branch-prefix>/<task-name>
-D is expected: after a squash- or rebase-merge, -d refuses even
though the work is merged.
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.
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.
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.