featree

Creates a feature bookmark and isolated git worktree with crosslink agent initialization.

1.4k|335|Updated Jun 10, 2014
One-click install
npx skills add https://github.com/openwpm/OpenWPM --skill featree-openwpm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: featree
Source: https://github.com/openwpm/OpenWPM/tree/main/.claude/skills/featree
Command: npx skills add https://github.com/openwpm/OpenWPM --skill featree-openwpm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up an isolated workspace for a new feature normally requires manually creating branches, worktrees, and agent configuration, which is error-prone and repetitive in multi-agent development workflows. ## Core Features & Use Cases - Feature Bookmark Creation: Invokes the feature skill to create a feat/<slug> bookmark from a human-readable feature description. - Git Worktree Provisioning: Checks out the feature branch into an isolated directory under <repo-root>/.worktrees/<slug> so changes do not affect the parent checkout. - Crosslink Initialization: Runs crosslink init, creates a derived agent identity (<parent-agent>--<feature-slug>), and syncs shared coordination state. - Use Case: When you ask to "make a worktree for add batch retry logic", the Skill creates the bookmark, spins up .worktrees/add-batch-retry-logic, and prepares a child agent to work there independently. ## Quick Start Ask the assistant to make a worktree for your feature, for example by saying "make a worktree for add batch retry logic".

Frequently Asked Questions about featree

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

FAQPage Schema
How do I create a git worktree for a new feature branch?

Run git worktree add with a target path and branch name, such as git worktree add .worktrees/my-feature feat/my-feature. This checks out the branch into an isolated directory with its own working tree and HEAD, leaving the parent checkout untouched.

How do I set up an isolated workspace for a child agent?

Create a git worktree for the feature branch, then run crosslink init --force and crosslink agent init with an ID like <parent-agent>--<feature-slug> inside the worktree. Finish with crosslink sync to pull the latest shared coordination state.

Does this work with jj colocated repositories?

Yes. In a colocated jj+git repository, the jj bookmark created by the feature skill auto-exports to a git branch, so git worktree add can resolve feat/<slug> directly. Git worktrees are used instead of jj workspaces for child-agent isolation.

Where should git worktrees be placed in a repository?

Worktrees should be placed inside <repo-root>/.worktrees/ so they inherit the project's Claude Code trust scope and settings hierarchy. The .worktrees directory should be added to .gitignore to keep it out of version control.

What are the limitations of this worktree workflow?

The workflow never force-pushes, deletes branches, or pushes to a remote; the user pushes manually when ready. Also, crosslink init --force replaces the project's .claude/settings.json hooks, so any existing hooks must be re-added afterward.