菜单
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.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/michaelshimeles/skills --skill new-feature命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Records visual proof while testing UI behavior — screen recording with structured test/assertion annotations — 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).
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.
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.
正在显示 SKILL.md
| name | new-feature |
| description | 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.