pool

Maintain persistent git worktree instances for parallel issue execution.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Jeqqe/jersal-project-template --skill pool
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pool
Source: https://github.com/Jeqqe/jersal-project-template/tree/main/.pi/skills/pool
Command: npx skills add https://github.com/Jeqqe/jersal-project-template --skill pool

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, pnpm, and includes scripts (resource) components.

What problem does it solve?

The pool eliminates slow, failure-prone “one worktree per issue” setups by providing a fixed set of reusable git worktrees that are prepared, leased, and reset reliably for parallel issue work.

Core Features & Use Cases

  • Persistent worktree pool: Creates and maintains detached worktrees under .worktrees/instance-N, each with its own node_modules for consistent parallel execution.
  • Fast leasing for batch runs: Leases an instance to a specific branch, hard-resets to a base ref, cleans untracked files, and runs pnpm install only when package dependencies changed.
  • Recovery and lifecycle management: Supports status inspection, resetting back to origin/release, repairing corrupted/wedged instances, and fully destroying the pool.

Quick Start

Ask your agent to initialize the pool by running: .pi/skills/pool/scripts/pool.sh init 4.

Frequently Asked Questions about pool

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

FAQPage Schema
How do I avoid slow git worktree setup when processing multiple branches in parallel?▼

A persistent git worktree pool eliminates slow setup by maintaining reusable detached worktrees under .worktrees/instance-N, each with its own node_modules, leasing them to specific branches for parallel execution without repeated cold setups.

How do I reset a leased git worktree to a clean state for a new task?▼

Leasing a worktree hard-resets the instance to a base ref, cleans untracked files, and runs pnpm install with --frozen-lockfile --prefer-offline only when package dependencies change, ensuring a predictable clean workspace.

What is the best way to manage multiple git worktrees for parallel issue execution?▼

Maintaining a persistent pool of git worktree instances provides predictable per-issue workspaces by creating detached worktrees, installing dependencies, and offering lease, reset, repair, and destroy operations for reliable batch workflow management.

Can I recover a corrupted or wedged git worktree in a parallel processing pool?▼

Yes, the worktree pool supports repairing corrupted or wedged instances, allowing recovery without fully destroying the pool, alongside status inspection and resetting back to origin or release refs.

Do I need pnpm to use a persistent git worktree pool?▼

Yes, pnpm is required as the worktree pool prepares instances by installing dependencies with pnpm --frozen-lockfile --prefer-offline to ensure consistent parallel execution environments across all leased worktrees.

How do I fully destroy a git worktree pool when batch processing is complete?▼

The pool provides a destroy operation that fully removes all persistent worktree instances under .worktrees/instance-N, cleaning up the parallel execution environment after batching workflows are finished.