multi-repo-dev

Orchestrate parallel development across multiple repositories using ghq, gwq, and tmux.

Updated Jan 26, 2013
One-click install
npx skills add https://github.com/boxp/dotfiles --skill multi-repo-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multi-repo-dev
Source: https://github.com/boxp/dotfiles/tree/main/.claude/skills/multi-repo-dev
Command: npx skills add https://github.com/boxp/dotfiles --skill multi-repo-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces the overhead of switching between repositories and enables parallel development across multiple repos using ghq, gwq, and tmux.

Core Features & Use Cases

  • Orchestrates per-repo worktrees via ghq and gwq for frontend/backend repositories.
  • Launches development servers in isolated tmux sessions for each worktree.
  • Provides cross-worktree status checks and session management to keep development synchronized.
  • Use Case: When building a microservice architecture, work on frontend and backend features concurrently while sharing commands and environments.

Quick Start

ghq get github.com/user/frontend-repo ghq get github.com/user/backend-repo cd $(ghq list -p | grep frontend-repo) && gwq add -b feature/api-integration cd $(ghq list -p | grep backend-repo) && gwq add -b feature/new-endpoint gwq tmux run -w feature/api-integration "npm run dev" gwq tmux run -w feature/new-endpoint "go run main.go" gwq status -g --show-processes gwq tmux list gwq exec feature/api-integration -- npm test

Frequently Asked Questions about multi-repo-dev

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

FAQPage Schema
How do I manage parallel development across multiple repositories?

Parallel development across multiple repositories is managed by orchestrating ghq, gwq, and tmux to create per-repo worktrees, launch isolated development servers in tmux sessions, and provide cross-workspace command execution for synchronized frontend and backend workflows.

How do I run development servers for different worktrees in isolated tmux sessions?

Running development servers in isolated tmux sessions is achieved using gwq tmux run. You attach a worktree to a tmux session and execute commands like npm run dev or go run main.go, keeping frontend and backend processes separate but synchronized.

What's the best way to work on frontend and backend microservices concurrently?

Working on frontend and backend microservices concurrently is best done by creating per-repo worktrees with gwq add, enabling coordinated worktrees for simultaneous feature development and reducing the overhead of switching between repositories.

Do I need ghq and tmux installed to use parallel multi-repo workflows?

Yes, ghq, gwq, and tmux must be installed and configured to use parallel multi-repo workflows, as these dependencies are required to create per-repo worktrees, launch isolated tmux sessions, and execute cross-workspace status checks.

Can I execute commands across all my active worktrees at once?

Yes, you can execute commands across active worktrees using gwq exec. This provides cross-worktree status checks and session management, allowing you to run tests or share commands across different repository workspaces simultaneously.

How do I check the status of running processes in my tmux development sessions?

Checking the status of running processes in tmux development sessions is done using gwq status -g --show-processes. This provides a cross-workspace view of your active worktrees and their associated development servers in each session.