create-worktree

Create a managed i3pm worktree from a task summary and switch context.

2|Updated Aug 18, 2025
One-click install
npx skills add https://github.com/vpittamp/nixos-config --skill create-worktree-vpittamp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-worktree
Source: https://github.com/vpittamp/nixos-config/tree/main/.codex/skills/create-worktree
Command: npx skills add https://github.com/vpittamp/nixos-config --skill create-worktree-vpittamp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a new worktree in the managed i3pm repository layout from a task summary, then switch your local context to the new worktree.

Core Features & Use Cases

  • Infer the target repository from the current workspace or active i3pm context and require user confirmation before mutating any state.
  • Propose a meaningful branch name via i3pm and determine the base branch (fallback to main if needed).
  • Create the worktree, refresh discovery, and switch the active local context to the new worktree.
  • Report the created qualified name, path, base branch used, discovery status, and switch success.

Quick Start

Provide a task summary and confirm before creating the worktree.

Frequently Asked Questions about create-worktree

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a worktree from a task summary and switch to it?

To create a worktree, provide a task summary so the tool can infer the repository context, propose a branch name, determine the base branch, and switch your local context after you confirm the mutation.

How does worktree creation infer the target repository?

Worktree creation infers the target repository from your current workspace or active i3pm context, ensuring the new branch is created in the correct managed repository layout.

Do I need to confirm before creating a new worktree?

Yes, user confirmation is required before mutating any state, ensuring you approve the proposed branch name and determined base branch before the worktree is actually created.

What happens if the base branch is not specified for worktree creation?

If the base branch is not explicitly specified, the worktree creation process falls back to using the main branch as the default base for building the new branch.

What details are reported after successfully creating a worktree?

After creating a worktree, the tool reports the qualified name, file path, base branch used, discovery refresh status, and the success of the local context switch.

Can I use this worktree approach without an active i3pm context?

You can use this approach if your current workspace provides enough repository context, but an active i3pm context is preferred to accurately infer the target repository and propose a branch name.