finishing-a-bones-leaf

Decide open bones swarm leaf handling with optional trunk materialization and PR creation.

4|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/danmestas/wardrobe --skill finishing-a-bones-leaf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-bones-leaf
Source: https://github.com/danmestas/wardrobe/tree/main/skills/finishing-a-bones-leaf
Command: npx skills add https://github.com/danmestas/wardrobe --skill finishing-a-bones-leaf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After a bones swarm session closes, decide what to do with the open leaf — fan-in to trunk, keep open, or abandon — and (optionally) materialize trunk into the git worktree, push, and open a PR for the swarmed changes. Use when implementation is complete, all tests pass, and you need to integrate the work back into the bones hub trunk.

Core Features & Use Cases

  • Guides post-swarm decisions: fan-in to trunk, keep the leaf open for later work, or abandon the leaf.
  • Supports optional trunk materialization into the git worktree and optional PR creation.
  • Handles branch creation, push, and PR orchestration to integrate changes back into trunk.

Quick Start

Review your current swarm leaf status and select an finalization path to complete the integration.

Frequently Asked Questions about finishing-a-bones-leaf

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

FAQPage Schema
How do I integrate a git worktree branch back into the main trunk?

Git worktree branch management involves deciding whether to fan-in changes to the trunk, keep the leaf open for later work, or abandon it, with optional trunk materialization and PR creation to finalize integration.

What is a bones swarm leaf and when do I need to finalize it?

A bones swarm leaf is an isolated work branch created during a swarm session. You need to finalize it after implementation is complete, tests pass, and you are ready to integrate the work back into the bones hub trunk.

How do I create a pull request from a git worktree after a swarm session?

Create a pull request from a git worktree by applying the swarmed changes, creating a new branch, pushing it, and orchestrating the PR creation to integrate the finalized work directly into the trunk.

Do I need a bones workspace to use git worktree branch management?

Yes, you need an active bones workspace and a configured git worktree as prerequisites to execute the scripted flow for applying changes, creating branches, and opening pull requests.

Can I keep a swarm leaf open instead of merging it into the trunk?

Yes, the finalization process supports keeping the leaf open for later work or abandoning it entirely, providing flexible branch management options beyond immediate trunk integration.

What are the limitations when abandoning a bones swarm leaf?

Abandoning a bones swarm leaf discards the open work without trunk materialization or PR creation, preventing the swarmed changes from integrating into the main hub trunk.