Skill2.3k estrellas del repoactualizado 1mo ago

worktree

This skill automates the creation and initialization of Git worktrees for parallel development in the AgentsMesh project. Use it when you need to establish an isolated development environment for a new feature or bug fix, allowing multiple branches to be worked on simultaneously without affecting the main working directory. The skill handles worktree creation, automatic environment configuration with isolated ports, Docker service initialization, database setup, and provides connection details for frontend, backend, and admin interfaces.

Ver fuente Repositorio: AgentsMesh

Instalar en Claude Code

Copiar

git clone --depth 1 https://github.com/AgentsMesh/AgentsMesh /tmp/worktree && cp -r /tmp/worktree/agents/skills/worktree ~/.claude/skills/worktree

Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

Definición

SKILL.md

# AgentsMesh Worktree

Create worktrees next to the main checkout under `AgentsMesh-Worktrees`.

## Workflow

1. Determine the requested branch name, base branch (default `main`), and
   whether the task actually needs a running development stack.
2. Inspect repository state and identify the base remote from the user's request,
   the base branch upstream, or its URL:

   ```bash
   git status --short --branch
   git remote -v
   git worktree list
   ```

   Preserve all existing changes. Do not stash, reset, commit, or clean the main
   checkout as a side effect of worktree creation.
3. Fetch the selected base:

   ```bash
   git fetch <base-remote> <base-branch>
   ```

4. Derive a filesystem-safe directory name by replacing `/` in the branch with
   `-`. Use `$(dirname "$repo_root")/AgentsMesh-Worktrees`; do not embed a
   user-specific absolute path.
5. Check whether the branch or path already exists. If the branch is new:

   ```bash
   git worktree add -b <branch-name> \
     <worktree-root>/<directory-name> \
     <base-remote>/<base-branch>
   ```

   If the branch already exists and is not checked out elsewhere, attach it
   without `-b`. Never delete or reset an existing branch to make the command
   succeed.
6. In the new worktree, verify:

   ```bash
   git status --short --branch
   git log --oneline -3
   git merge-base --is-ancestor <base-remote>/<base-branch> HEAD
   ```

7. Start the environment only when runtime verification is needed. Read
   `references/dev-environment.md`, run the appropriate Bazel lifecycle target,
   then load and report the generated `deploy/dev/.env` values.

## Result

Report the absolute worktree path, branch, base ref and commit, whether the
development stack was started, and the generated ports when applicable. Do not
remove the worktree automatically; cleanup must preserve uncommitted or
unpushed work.

Del mismo repositorio

github-gitlab-mirrorSkill