Run parallel ship pipelines on leased worktrees and integrate branches into one PR.
npx skills add https://github.com/Jeqqe/jersal-project-template --skill batch-jeqqe
Please help me install this Agent Skill. Skill: batch Source: https://github.com/Jeqqe/jersal-project-template/tree/main/.pi/skills/batch Command: npx skills add https://github.com/Jeqqe/jersal-project-template --skill batch-jeqqe
This Skill removes the bottleneck of handling multiple GitHub issues sequentially by running each issue’s work in parallel and then combining the results into one integration pull request.
ship runs concurrently using a persistent pool of instances for isolation and speed.integrate to merge the set into one shippable PR and close the issues.Run /skill:batch <issue-numbers> to process a partitioned set of issues concurrently (max 4 by default), then create a single integration PR that closes them.
High-intent search queries and answers about installing and using this skill.
You can process multiple GitHub issues in parallel by fanning out ship pipelines across leased worktree instances, then integrate the resulting branches into one consolidated PR that closes all issues.
Handling issue dependencies in parallel CI pipelines requires validating explicit dependency declarations, detecting cycles, and scheduling dependent issues to run only after their prerequisites report READY.
Running isolated background sub-agents for concurrent GitHub issue resolution involves leasing separate worktree instances from a persistent pool, spawning tasks in parallel, and resetting instances upon completion.
Yes, you can integrate multiple feature branches into a single shippable PR by waiting for all parallel branches to report READY, then invoking an integrate command to merge the set and close the issues.
Dependency cycles block parallel GitHub issue processing because the system validates in-batch dependencies and schedules dependent issues only after prerequisites complete, preventing circular execution.
Yes, you must claim GitHub issues before starting parallel ship execution, as the workflow requires claiming issues, validating dependency constraints, and leasing pool instances prior to spawning sub-agents.
AztecProtocolSpawn a Claude instance in a separate git worktree for parallel task execution.
fredericosantosCreate a PR from a milestone branch and close associated issues.
neubigDelegate parallel tasks to sub-agents via DelegateTool or OpenHands Cloud API.
tranhieuttOrchestrate parallel git worktrees with subagents and sequential merges.