git-trees

Organize related worktrees across multiple QoL repositories into feature lanes.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/qol-tools/qol-skills --skill git-trees
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-trees
Source: https://github.com/qol-tools/qol-skills/tree/main/plugins/qol-dev-conventions/skills/git-trees
Command: npx skills add https://github.com/qol-tools/qol-skills --skill git-trees

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate changes across multiple QoL repositories by organizing related work into a single feature lane.

Core Features & Use Cases

  • Group related worktrees by feature across repositories.
  • Maintain one branch name per feature lane for coordinated testing.
  • Provide a canonical directory layout and creation flow to simplify cross-repo work.

Quick Start

Choose a feature branch name, create the shared worktrees directory, and for each participating repo create a per-repo worktree inside that directory using the same branch name.

Frequently Asked Questions about git-trees

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

FAQPage Schema
How do I coordinate git worktrees across multiple repositories for a single feature?

To coordinate git worktrees across multiple repositories, group related worktrees by feature into a shared directory, using one consistent branch name per repo to enable aligned testing across the entire feature lane.

What is a feature lane in multi-repo development workflow?

A feature lane in multi-repo development organizes changes spanning multiple repositories into a single coordinated track, applying a canonical layout and per-repo worktrees to simplify cross-repo testing.

How do I set up a canonical directory layout for multi-repo feature development?

Set up a canonical directory layout for multi-repo work by creating a shared worktrees directory, then generating a per-repo worktree inside it for each participating repository using the same branch name.

Does multi-repo worktree coordination require branch-name alignment across all repositories?

Yes, multi-repo worktree coordination requires branch-name alignment across all participating repositories, ensuring that each per-repo worktree uses the same branch name to maintain a single feature lane for testing.

Can I use a feature lane for A/B testing across qol-tray, plugins, and shared repos?

Yes, you can use a feature lane for A/B testing across qol-tray, plugins, and shared repositories by organizing related worktrees under one branch name to enable coordinated testing.

What's the best way to manage cross-repo experiments without losing track of related changes?

The best way to manage cross-repo experiments is organizing related work into a single feature lane, grouping per-repo worktrees by feature with branch-name alignment to maintain coordinated testing across repositories.