Results for “worktree”

Manage separate local development environments for multiple branches using the project's pnpm worktree CLI. Each environment has its own ports and dependencies, with options to share Supabase or isolate database changes for testing.

• Running and testing multiple branches at the same time
• Testing database migrations in a separate database
• Reusing an existing worktree for related fixes

新しい worktree を作成する。「worktree 作成」「worktree を作って」「worktree 切って」「Issue から worktree」「作業用 worktree」「gtr new」などで起動。Issue 番号・ブランチ名の直接指定・コンテキストからの自動命名に対応。一覧・削除・クリーンアップは shiiman-git:worktree。

The English summary is being prepared. Showing the original description.

Manage Orca worktrees, separate working directories, along with terminals, repositories, and its embedded browser through the CLI. Use it to hand work to another agent, manage artifacts, run automations, and share skills within Orca.

• Starting codex or claude in a child worktree
• Reading terminal output and sending input
• Operating Orca's embedded browser

gtr で worktree を一覧・削除・クリーンアップする（管理操作）。「worktree 一覧」「gtr list」「gtr rm」「worktree 削除」「worktree クリーンアップ」「マージ済み worktree 削除」などで起動。新規作成は shiiman-github:worktree-create を使う。

The English summary is being prepared. Showing the original description.

マシン上の git worktree とローカルブランチを横断で棚卸しし、マージ済みかを判定して安全に削除する。「worktree を整理して」「マージ済みブランチを消して」「worktree を全部リストして」等の依頼時、/worktree-audit 実行時に使用。境界: 単一 worktree の作成・片付け手順は context/worktree-guide.md、コードベースの監査は codebase-review。

The English summary is being prepared. Showing the original description.

Set up a separate Git working directory for a new task or an existing branch, pull request, or commit. Detect and reuse existing isolation, prefer the agent environment's worktree tools, and report the working path and branch.

• Starting a feature in a separate working directory
• Isolating an existing branch or commit
• Preparing a separate workspace for pull request review

Creates a separate Git working directory for a task and moves the agent session into it using Worktrunk. Supports choosing another repository, naming the branch, and carrying uncommitted changes into the new workspace.

• Starting a task in a separate working directory
• Creating a worktree in another repository
• Moving uncommitted work into a new worktree

Create, manage, and cleanup git worktrees with Claude Code agents across all projects. USE THIS SKILL when user says "create worktree", "spin up worktrees", "new worktree for X", "worktree status", "cleanup worktrees", "sync worktrees", or wants parallel development branches. Also use when creating PRs from a worktree branch (to update registry with PR number). Handles worktree creation, dependency installation, validation, agent launching in Ghostty, and global registry management.

The English summary is being prepared. Showing the original description.

HTCMC PCHSystem 专用 skill——指导如何在 git worktree 中正确启动/迁移开发栈 （根 docker-compose 的 postgres+backend、TestServer 的 mc-test、前端 Vite dev）。 PCHSystem 的栈路径锚定主仓（bind mount / external 网络 / MCDR 挂载 / 根 .env 插值）， worktree 的目录隔离与之天然冲突，常踩「端口对不上 / token 对不上 / 配置在别的分支」三类坑。 本 skill 给出按「worktree 改了什么」选择的迁移策略 + 端口/token/网络对齐清单 + 红线陷阱。 当用户在 worktree 里要起栈测试、提到「worktree 跑后端/前端/mc-test」「worktree 端口冲突」 「token 对不上 / 401」「主仓有 WIP 没法 checkout 分支」「MCDR reload 看不到 worktree 改动」， 或要在 worktree 改了 Dockerfile / pyproject / 端口 / .env 后验证时，就应使用本 skill。 不用：纯文档或单文件编辑、不涉及运行栈的常规开发、或仅在主仓主线本地开发（不起 worktree）。

The English summary is being prepared. Showing the original description.

Set up Herdr Kit and its Mastra Code integration, manage repository synchronization, and create or remove managed worktrees, separate working copies for review or development. The workflow checks supported operations and verifies the resulting manager state.

• Installing Herdr Kit and the Mastra Code integration
• Keeping repositories synchronized after closing their workspaces
• Creating or removing managed Review and Work worktrees

Manage parallel feature development with Git worktrees, separate working folders for different branches. Assign distinct ports, copy environment files, optionally install dependencies, and check for uncommitted changes and merged branches before removing outdated worktrees.

• Develop several feature branches at the same time
• Prepare a separate workspace for an urgent hotfix
• Give each AI agent its own branch and working folder

Manage Git worktrees, separate working folders for branches, with Worktrunk’s wt CLI. Get guidance on command targets, configuration, automated hooks, aliases, commit message generation, and troubleshooting when commands behave unexpectedly.

• Identifying which worktree a command will affect
• Automating setup and checks with project hooks
• Configuring AI-generated commit messages

Prepare a separate Git working directory for feature development, then install project dependencies and run baseline tests. Check for existing isolation first, use native worktree tools when available, and otherwise fall back to Git.

• Starting feature development in a separate working directory
• Preparing a workspace before executing an implementation plan
• Reusing an existing isolated workspace

Manages git worktrees for parallel agent isolation. Creates isolated worktrees for parallel agents on parallel/{name}-{timestamp} branches, merges results with conflict detection, prunes stale metadata, and reports health status. NOT for user-initiated feature branches — use git worktree directly for that.

The English summary is being prepared. Showing the original description.

Prepare a separate workspace for feature development using platform tools or git worktree, which gives a branch its own working directory. It checks existing isolation, prepares dependencies, and runs tests before implementation begins.

• Starting feature work in a separate workspace
• Preparing a workspace before executing an implementation plan
• Checking whether a workspace is already isolated

Coordinate a small Qwen Code team using shared tasks and peer messages. Read-only teammates investigate separate questions, while an optional single writer implements changes in a separate Git worktree for review and verification.

• Split an investigation into clearly owned tasks
• Resolve conflicting findings through teammate messages
• Pass accepted research to a single implementation writer

Verify, customize, or opt out of moflo's AUTOMATIC durable-learning sharing across git worktrees / Conductor workspaces on one machine. As of the worktree-auto-sharing change this is on by default — learnings converge across a repo's worktrees with no setup. Use when the user asks "is memory shared across my worktrees?", "where are my worktree learnings stored?", "turn off worktree memory sharing", "share learnings across my separate clones", or "point my worktrees at a custom store". For a team or cross-machine (git-tracked) sharing, use /memory-team instead.

The English summary is being prepared. Showing the original description.

Coordinate multiple AI agents with assigned owners, clear work boundaries, and a Kanban board that tracks progress. Organize separate branches or worktrees, collect test and handoff evidence, and define checks that must pass before combining their work.

• Assign parallel tasks to multiple AI agents
• Track progress and blockers across sessions
• Separate editing work across branches or worktrees

Organize a task into parallel work streams with clear dependencies, separate places for changes, and explicit checks. Batch independent reads and tests, coordinate concurrent work, and report completed or blocked tasks with verification results.

• Batching independent file reads and searches
• Splitting implementation across multiple agents
• Separating changes with Git worktrees

Cancel an active PUA loop from Codex CLI using an alias for the corresponding Claude Code command. The workflow cleans loop state and worktree references, records the cancellation, and requires execution evidence before claiming completion.

• Stopping an active PUA loop
• Cleaning loop state and worktree references during cancellation
• Recording cancellation and checking execution evidence

Run independent development tasks in parallel, each with a separate git worktree and implementation agent. Each agent opens its own pull request, which receives cross-review before being handed to a human for review and merging.

• Implementing independent changes in parallel
• Assigning separate working directories to agents
• Preparing an individual pull request for each task

Manage git worktrees across any repository with the `gwm` Rust binary (CLI + ratatui TUI). Use when the user asks to create / list / remove / bootstrap / switch / link worktrees, run a command across worktrees (`gwm exec`) or reclaim build artifacts (`gwm clean`), materialise a PR into a worktree (`gwm review`), drive a multi-repo workspace (`--workspace`), run the JSON daemon / statusline (`gwm daemon`, `gwm statusline`), list or pin AI-agent sessions per worktree (`gwm agents`, Claude Code / Codex / opencode / Mistral Vibe detection), seed config from a preset (`gwm init --preset`), diagnose with `gwm doctor`, drive tmux/zellij, or wire `gcd` via `gwm shell-init`. Also covers multi-forge (#419): GitHub via `gh` **or** GitLab via `glab`, the `forge` / `[forge_hosts]` keys, and `gwm trust add`. Triggers on `gwm`, `gwq`, `git worktree`, `.gwm.toml`, `forge`, `forge_hosts`, `glab`, `gwm trust add`, GitLab MR, `gwm create`, `gwm list`, `gwm exec`, `gwm clean`, `gwm review`, `gwm daemon`, `gwm statusline`, `gwm agents`, `gwm note`, `gwm bootstrap`, `gwm doctor`, `gwm switch`, `gwm tmux`, `gwm zellij`, `gwm link`, `gwm status`, `gwm shell-init`, `gcd`, `feat/#`, `fix/#`, GitHub issue/PR linking on a worktree.

The English summary is being prepared. Showing the original description.

Gives a repository one idempotent, repo-local worktree setup script (local env files, dependency install, build steps) that worktrunk's `.config/wt.toml` pre-start hook and Orca's `orca.yaml` scripts.setup both call, so every new git worktree is usable at once. Use when adding or fixing worktree setup hooks, writing `wt.toml` or `orca.yaml` setup, when new worktrees lack dependencies or `.env` files, or when asked to make worktrees "just work" in a repo. For creating a worktree in a repo that already has setup, use `git-branch-management` instead.

The English summary is being prepared. Showing the original description.

Take implementation work through small, independently mergeable pull requests. Use a separate working directory for each PR, record manual QA evidence, write English review descriptions, resolve CI and review findings, then merge and clean up.

• Deliver implementation work through pull requests
• Split a large task into small, independently mergeable PRs
• Build independent PRs concurrently