Results for “worktree”

Use when the user reports a problem or names a piece of work and wants to start on it in a fresh worktree — "start a task", "new task", "file this and make a branch", "/start-task". Finds or files the GitHub issue, creates the feat/… or bugfix/… branch linked to it, and prints the paste-ready `ai fwt|bwt` (Docker) and `ai os fwt|bwt` (host) commands that open the worktree. Linear flow with hard stops; asks nothing.

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

[Deprecated] worktree management is part of execution. Use `cm-execution` instead.

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

Create and manage git worktrees for parallel agent sessions

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

Parallel SDLC batch runner. Analyzes a list of independent task descriptions, groups them by heuristic file-conflict prediction, dispatches one worktree-isolated background agent per task (each running the full pipeline-orchestrator: BA → Dev → QA → Sec → Docs), and aggregates results into a single batch summary. Use when: - `/sdlc:batch` invokes this skill after parsing its arguments (Step 2 of commands/batch.md) - You have 2+ independent feature/fix descriptions to run through the SDLC pipeline in parallel Do NOT use for: - A single task (use pipeline-orchestrator directly via /sdlc:start) - Tasks that must share a single working tree (this skill isolates each task in its own git worktree)

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

Create isolated git worktrees with smart directory selection and safety verification

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

Use when work needs an isolated git worktree: new work, an existing ref, a gated feature workspace, a manifest-tracked loop run, or a candidate patch captured without touching the current checkout (`capture-isolated-patch`). Not for plain branches: use create-branch. Not for remote, credential, publish, deploy, or irreversible changes.

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

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

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

Use when legacy prompts or older framework flows reference `using-git-worktrees` and you need the modern runtime to resolve that capability cleanly.

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

Run a regelrecht branch locally end-to-end (worktree + Docker stack + DB), with the workarounds needed when developing inside the dev container against Docker Desktop. Accepts a branch name or a PR number. Subcommands: bare arg = start, `stop <arg>` = shut down, `clean <arg>` = shut down and remove worktree.

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

Guided setup for sharing moflo's durable learnings through a git-tracked artifact — for a whole TEAM on one repo, OR for one person across several MACHINES (a team of one). Use when the user says "share learnings with my team", "commit our moflo memory", "sync memory across my laptop and desktop", "set up memory.team_artifact", "auto-export learnings on every PR", or "learnings.jsonl keeps conflicting". Installs a pre-commit hook so the artifact rides along in every commit. An existing learnings.jsonl moves to the conflict-free layout automatically. For many worktrees on ONE machine, use /memory-worktree.

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

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

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

worktree 준비 경로 fixture에 기존 파일을 심는 법과 spawn-block 정리 판정 3종

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

committed 단일 커밋의 스키마 의존 RED는 detached 리뷰 worktree에서 배선 토글 3점으로

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

base 전진 시 retained worktree diff의 3-way 재이식

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

commit-range 독립 리뷰는 detached worktree에서 게이트 실행

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

Grind through ready beads serially in priority order, one at a time in the current worktree, without stopping between issues. Use when asked to work the beads queue, grind the backlog, keep working through ready issues, or make unattended progress overnight. For concurrent worktrees instead, use beads-parallel-grinding.

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

Coordinates staged or parallel jobs across live-verified coding-agent runtimes (Claude Code, Codex, Cursor, and other installed CLIs) and in-session toolkit subagents. Routes each job by capability and risk tier, isolates parallel writers in git worktrees, captures redacted output, resumes interrupted runs, and blocks completion until an independent arbiter verifies the results. Use when work should be split across multiple runtimes or subagents, run as staged or parallel jobs, and reviewed before handoff. NOT for a single-agent task or the in-session 7-phase flow (use mk:cook / mk:workflow-orchestrator).

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

Execute a swarm plan wave by wave with filesystem isolation via git worktrees. For each wave, main context decides the scenario recipe + implementation contract for every task, then spawns one swarm-worker per task in parallel. Each worker executes its recipe and reports JSON status. Worktree merge-audit verifies write-set discipline before changes land on main. Aborts remaining waves on any audit or task failure.

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

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

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

并行会话巡检：扫 .forge/active.md，按硬信号（worktree 是否存在、分支是否已合并）判僵尸，一次确认批量清理并联动 backlog；不用时间戳启发式。 触发方式：用户说"forge 状态"、"看下谁在跑"、"清理 worktree"、"forge-status"；forge-bugfix 启动时只读巡检。

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

并行会话巡检：扫 .forge/active.md，按硬信号（worktree 是否存在、分支是否已合并）判僵尸，一次确认批量清理并联动 backlog；不用时间戳启发式。 触发方式：用户说"forge 状态"、"看下谁在跑"、"清理 worktree"、"forge-status"；forge-bugfix 启动时只读巡检。

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

When starting parallel work in isolation from the current branch — spawn a git worktree with ignore-safety checks and a clean test baseline — even when the user says 'try this on the side'.

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

Use when governing a worktree across its whole life — scope-lock declaration, merge-readiness status, scoped verification, and safe cleanup that refuses while unique unmerged commits exist.

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

Recreate a worktree for a given PR to test it locally — useful after /implement auto-cleaned the worktree. Usage: /open <PR>

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