From e6096fd989c7140d285e4bc137bfbee0fa9d262e Mon Sep 17 00:00:00 2001 From: Tommaso Casaburi Date: Thu, 30 Apr 2026 14:11:46 +0700 Subject: [PATCH] docs(agents): require descriptive worktree names --- AGENTS.md | 1 + 1 file changed, 1 insertion(+) diff --git a/AGENTS.md b/AGENTS.md index 7f9be7df..5ccaeeb4 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -108,6 +108,7 @@ src/ - Prefer short-lived task branches over a long-lived `develop` branch unless the user explicitly asks for a staging branch workflow. - Use worktrees only when parallel tasks need isolated checkouts. One active task branch per worktree. - If a new task is unrelated to the currently checked out branch, do not stack it on that branch. Create a new worktree from `master` and create a separate short-lived task branch there. +- Always give a new worktree a descriptive name that reflects the task (e.g. `fix-login-redirect`, not `wt1`, `tmp`, `feature`, or a numbered slug), so it can be identified at a glance in a long list of worktrees. When using `./scripts/create-task-worktree.sh`, the `` argument must be that descriptive name. - Prefer `./scripts/create-task-worktree.sh ` when you need a new task worktree and do not have a stronger repo-specific reason to create it manually. - Treat branch and worktree as different things: the branch is the change set; the worktree is the checkout where that branch is worked on. - For parallel unrelated tasks, give each task its own branch from `master`, its own worktree, and its own PR into `master`.