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.
The English summary is being prepared. Showing the original description.
Review 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.
Captures before/after screenshots of web pages or elements for visual comparison. Use when user says "take before and after", "screenshot comparison", "visual diff", "PR screenshots", "compare old and new", or needs to document UI changes. Accepts two URLs (file://, http://, https://) or two image paths.
The English summary is being prepared. Showing the original description.
Use when multiple workflows duplicate the same operational logic, when deciding what belongs in actions vs shared services, or when refactoring repeated operational blocks across domain flows. Use when adding new features that share mechanics with existing ones.
The English summary is being prepared. Showing the original description.
Records visual proof while testing UI behavior — the agent tests the app hands-on via computer use while a screen recording with structured test/assertion annotations captures the session — then posts the video and a results summary to the requested destination. Use when changed runtime behavior needs observable verification, including headless environments (scripted screenshots and probes) and non-UI changes (measured numbers, output pairs).
The English summary is being prepared. Showing the original 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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Cut AI tells from text you write or edit for a human reader (commit messages, PR titles and bodies, docs, code comments, replies). Apply before committing, posting, or sending; leave prose you didn't touch alone.
The English summary is being prepared. Showing the original description.