kevmoo/kevmoo_skills/new-worktree

Pre-Flight & Hard Boundaries

Before creating any branch or worktree, verify the current working repository against the following boundaries:

1. Git Exclusivity:

• Must be a Git repository (git rev-parse --is-inside-work-tree).
• If not using Git, stop immediately and alert the user.

1. Repository Location (Must be under `~/github`):

• Check the absolute file path of the repository root.
• Repositories must reside under ~/github (arbitrarily deep, such as

~/github/kevmoo/kevmoo_skills or ~/github/repo).

• Hard Block: If the repository is located anywhere else, stop and issue

a warning asking for explicit human confirmation before proceeding. This prevents mutating internal corporate repositories or bare-repo dotfiles.

1. Dart SDK Exception:

• Check if the repository maps to the Dart SDK

(https://github.com/dart-lang/sdk, e.g., located at ~/github/dart-sdk).

• Hard Block: If operating in the Dart SDK repository, stop immediately

and ask if the user wants to use their specialized Dart SDK flow instead (e.g., dart-sdk-bootstrap). Do not proceed without clarification. The Dart SDK relies on specialized toolchains, gclient checkouts, and dedicated bootstrap workflows that standard Git worktree operations break.

Location & Naming Conventions

When creating a worktree, observe strict placement and naming rules:

• Location: Place the new worktree directory right next to the source

repository directory (as a direct sibling in the parent folder).

• Worktree Naming: Format the folder name as

_[original repo folder name]-[branch-name].

• Branch Naming: Derive a clean, hyphen-separated branch name from the user

request (e.g., issue-12345 or fix-auth-crash).

Examples

• In ~/github/flutter, invoking /new-worktree to fix flutter issue #12345:
• Creates branch: issue-12345
• Creates worktree at: ~/github/_flutter-issue-12345
• In ~/github/kevmoo/kevmoo_skills, invoking /new-worktree add lint check:
• Creates branch: add-lint-check
• Creates worktree at: ~/github/kevmoo/_kevmoo_skills-add-lint-check

Execution Steps

1. Verify Pre-Flight Boundaries: Confirm location under ~/github, confirm

Git repository status, and ensure the repo is not the Dart SDK. Do not require a clean working directory; worktrees allow branching safely from a dirty tree.

1. Fetch Latest Remote State & Resolve Base Branch: Prefer origin on

standalone personal repositories and forks under ~/github/<owner>/<repo> (unless remote.upstream.gh-resolved is base), and prefer upstream on external contribution checkouts at ~/github/<repo> so branches never start from a lagging origin/main, then resolve <remote>/HEAD, <remote>/main, or <remote>/master: ``bash REPO_ROOT=$(git rev-parse --show-toplevel) REMOTE="origin" if git remote | grep -qx upstream; then case "${REPO_ROOT}" in "${HOME}"/github/*/*/*) REMOTE="upstream" ;; "${HOME}"/github/*/*) if [ "$(git config --get remote.upstream.gh-resolved || true)" = "base" ]; then REMOTE="upstream" fi ;; *) REMOTE="upstream" ;; esac fi git fetch "${REMOTE}" TARGET_BASE=$(git symbolic-ref "refs/remotes/${REMOTE}/HEAD" 2>/dev/null || (git show-ref --verify --quiet "refs/remotes/${REMOTE}/main" && echo "${REMOTE}/main") || echo "${REMOTE}/master") ``

1. Formulate Target Names: Determine {branch_name} and sibling directory

path {sibling_worktree_path} based on naming rules.

1. Collision Pre-Flight & Stale Worktree Pruning:

• Check if {sibling_worktree_path} or local {branch_name} already exists.
• If previous worktrees were removed manually, run git worktree prune to

clear stale metadata.

1. Execute Worktree Creation:

``bash git worktree add -b {branch_name} {sibling_worktree_path} ${TARGET_BASE} ``

1. Configure Default GitHub Repository (`gh repo set-default`):

• Inside the newly created worktree directory ({sibling_worktree_path}),

configure gh to use the origin remote as the default repository so subsequent gh pr and gh run commands work without requiring -R: ``bash cd {sibling_worktree_path} && gh repo set-default origin ``

1. Output Clickable Link: Provide the user with a clickable link to the new

worktree using the precise scheme [link text](file:///absolute/path/to/worktree). Never wrap link text or syntax in backticks.