vw-worktree-ops

Automate vw worktree creation, switching, locking, cleaning, and command execution with JSON output.

64|2|Updated Feb 8, 2018
One-click install
npx skills add https://github.com/yuki-yano/dotfiles --skill vw-worktree-ops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vw-worktree-ops
Source: https://github.com/yuki-yano/dotfiles/tree/main/.agents/skills/vw-worktree-ops
Command: npx skills add https://github.com/yuki-yano/dotfiles --skill vw-worktree-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates safe and reproducible vw worktree management to streamline creation, switching, verification, locking, cleaning, and command execution across git worktrees.

Core Features & Use Cases

  • Safe worktree creation and switching with deterministic outcomes
  • JSON-first reporting for automation and auditing
  • Guardrails that prompt for explicit confirmation before destructive actions

Quick Start

Initialize the vw environment and begin safe worktree operations using vw status --json and subsequent vw commands.

Frequently Asked Questions about vw-worktree-ops

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

FAQPage Schema
How do I safely automate git worktree creation and switching?

You can automate safe git worktree operations by running vw commands that enforce preconditions and prompt for explicit confirmation before destructive actions, ensuring reproducible creation and switching.

What is the best way to get JSON output from git worktree management for automation?

Git worktree management produces JSON-first output via the --json flag on vw commands, providing structured data ideal for pipeline automation and auditing worktree states.

Can I execute shell commands across multiple git worktrees at once?

Yes, you can execute commands on worktrees using vw command execution features, which target specific worktrees and run operations within them while maintaining safety guardrails and JSON reporting.

Does vw worktree management prevent accidental data loss during cleanup?

Vw worktree management prevents accidental data loss by implementing explicit prompts and safety checks before destructive cleaning actions, verifying preconditions and locking active worktrees to guard against unintended removal.

Why do I need to lock a git worktree in an automated workflow?

Locking a git worktree prevents concurrent automated processes from modifying or cleaning an active worktree, ensuring reproducible outcomes by blocking destructive commands until the lock is explicitly released.

Do I need a specific environment to use vw worktree operations?

Yes, you need a vw-enabled environment initialized via vw commands, where worktree operations depend on this setup to apply safety checks, manage locking, and generate reproducible JSON output.