Creates and integrates full-repository Git worktrees for parallel monorepo development.
npx skills add https://github.com/nebius/nebius-ps-services --skill worktree-nebius
Please help me install this Agent Skill. Skill: worktree Source: https://github.com/nebius/nebius-ps-services/tree/main/skills/worktree Command: npx skills add https://github.com/nebius/nebius-ps-services --skill worktree-nebius
$worktree add from a clean primary checkout to create a generated child branch and full linked worktree pinned to the exact captured source SHA, with an optional --project starting directory and exact --reuse support. - Serialized Integration: Run $worktree integrate <name> from the primary checkout to safely commit eligible child and source changes, build a private two-parent merge candidate, validate it non-mutatingly, and fast-forward the source branch only to the exact validated SHA. - Proof-Gated Removal: Run $worktree remove <name> to delete a child worktree and its local ref only when it is unchanged from its base or its recorded merge remains reachable from the source branch. - Use Case: A developer needs to update Terraform modules and Helm charts concurrently in one monorepo. They create two worktrees, develop in each returned directory, integrate each child serially into the local feature branch, then publish that single accumulated branch. ## Quick Start Ask the agent to run $worktree add with a short task description from your clean feature branch checkout to create a linked worktree and start working in the returned directory.High-intent search queries and answers about installing and using this skill.
Invoke $worktree add with an optional task description from a clean primary checkout on a named non-default branch. The helper captures the exact current source SHA, creates a generated child branch and full linked worktree, and returns the starting directory for subsequent development commands.
Run $worktree integrate with the exact generated name from the primary checkout. The helper commits eligible dirt, builds a private two-parent merge candidate, requires non-mutating validation, and fast-forwards the source branch only to the exact validated SHA.
No. Child worktrees created by this workflow are never pushed or used for pull requests, and managed-child push or PR creation is blocked by guards. Only the accumulated local source branch is published through separate Git or PR skills.
The helper retains a private recovery candidate worktree and integration reservation. You resolve conflicts only in that returned candidate, stage the resolution, then rerun the same integration command; never resolve in the primary or child checkout.
Do not use it from the default branch, a detached HEAD, or a dirty primary checkout, since add requires a completely clean named non-default branch. It also does not support implicit invocation, cross-agent handoff, or sparse checkouts via --project.
Removal is proof-gated: the child must be unchanged from its captured base or its recorded merge must remain reachable from the source branch. Dirty, advanced, rewritten, leased, or unverifiable resources are retained to prevent work loss.
luicabref97Merge selected files, hunks, or commits from git worktrees into the current branch.
arka6fxPush the current branch to GitHub and create a pull request via gh.
AbildtoftRun formatting, linting, type-checking, builds, and tests on affected code.
vinzenzSummarizes git branch state, recent commits, and scratch notes for worktree orientation.