worktree-batch

Orchestrate parallel git worktree tasks with opencode and kiro-cli prompts.

1|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/consuelohq/opensaas --skill worktree-batch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: worktree-batch
Source: https://github.com/consuelohq/opensaas/tree/main/.claude/skills/worktree-batch
Command: npx skills add https://github.com/consuelohq/opensaas --skill worktree-batch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables teams to run and oversee multiple code-worktree jobs in parallel, isolating changes to accelerate batch updates and reviews.

Core Features & Use Cases

  • Orchestrates multiple opencode sessions across separate git worktrees for concurrent development tasks.
  • Centralizes specs, prompts, reviews, and merges to streamline batch operations and maintain traceability.
  • Supports deterministic task execution and isolation of changes to minimize interference between tasks.

Quick Start

Run a batch of parallel worktrees using the setup.sh and then run kiro-cli prompts followed by opencode reviews in each directory.

Frequently Asked Questions about worktree-batch

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

FAQPage Schema
How do I run parallel git worktrees for batch software tasks?

To run parallel git worktrees, execute setup.sh to create isolated worktree directories, then run kiro-cli-driven prompts followed by opencode-based reviews in each directory to process batch software tasks concurrently with traceable commits.

What is git worktree orchestration for concurrent development?

Git worktree orchestration coordinates multiple opencode sessions across separate git worktrees to execute concurrent development tasks, ensuring isolated changes and deterministic batch updates while maintaining centralized specs, prompts, reviews, and merges.

Can I use opencode to review isolated code changes across multiple worktrees?

Yes, opencode reviews isolated code changes by running separate sessions in each git worktree directory, enabling concurrent batch updates with deterministic task execution and traceable commits without interference between parallel tasks.

How do I automate batch code updates with kiro-cli prompts and git worktrees?

Automate batch code updates by running setup.sh to configure parallel worktrees, executing kiro-cli-driven prompts for task generation, and applying opencode-based reviews to ensure deterministic, isolated changes with traceable commit history.

What is the best way to isolate parallel code workload execution in git?

The best way to isolate parallel code workloads is using git worktrees to create separate working directories, orchestrating multiple opencode sessions to process batch tasks concurrently while maintaining deterministic execution and traceable commits per task.

When should I avoid using parallel worktree orchestration for software tasks?

Avoid parallel worktree orchestration when tasks require shared mutable state across worktrees, lack deterministic outcomes, or when batch updates need sequential dependency resolution that prevents isolated concurrent execution with traceable commits.