Start a new task in an isolated Git worktree branched from origin/main so multiple agents can work on the same repo in parallel without conflicts. Use at the beginning of every new feature, fix, or task — before writing any code.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Every task gets its own worktree and branch, created from the latest
origin/main. Never build on main, and never reuse another agent's
worktree or branch.
.claude/worktrees/<name>). Skip steps 3–4 below (no manual
git worktree add / remove), and keep the harness-assigned branch name.
Steps 1–2 and 5 still apply.worktree-*): same idea —
keep the assigned branch and worktree, apply steps 2 and 5.Sync: git fetch origin.
Scope check: run gh pr list and skim the open PRs' changed files
(gh pr diff <n> --name-only). If your task needs files another open PR
is editing, stop and ask for direction instead of proceeding. Also
check for uncommitted work in the checkout — another agent may be
mid-task.
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 gitignored directory for worktrees (e.g. .claude/worktrees/
or .worktrees/) so they can never be committed by accident, and 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
Then install dependencies fresh inside the worktree (worktrees don't
share node_modules/virtualenvs) and confirm the runtime version the
repo requires before running anything.
Worktrees do not isolate shared resources: dev-server ports, shared
databases, and dependency lockfiles are global. 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.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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 PR and tracker issue. Use whenever a change needs verifiable evidence that it works, instead of prose claims — including headless environments (scripted screenshots and probes) and non-UI changes (measured numbers, output pairs).
日本語の概要は準備中です。原文の説明を表示しています。
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments. Triggers Greptile review, fixes all actionable comments, pushes/re-shelves, re-triggers review, and repeats. Use when the user wants to fully optimize a PR/MR/CL against Greptile's code review standards.
日本語の概要は準備中です。原文の説明を表示しています。
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments. Identical to greploop, but triggers reviews by tagging @greptile-apps, which bypasses Greptile's file-count limit on huge PRs that the plain @greptile mention refuses to review. Use when the user wants to fully optimize a large PR/MR/CL against Greptile's code review standards.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。