virtual-workspace

Unify Claude Code and Codex agents, commands, skills, and hooks across sibling git repositories.

13|Updated May 5, 2026
One-click install
npx skills add https://github.com/filipealva/virtual-workspace --skill virtual-workspace
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: virtual-workspace
Source: https://github.com/filipealva/virtual-workspace/tree/main/skills/virtual-workspace
Command: npx skills add https://github.com/filipealva/virtual-workspace --skill virtual-workspace

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes assets (resource) components.

What problem does it solve?

Managing multiple git repositories for development often means juggling separate AI coding assistant (Claude Code, Codex) sessions, manually syncing custom agent, command, skill, and hook configurations across repos, and handling cross-repo feature branch work without context switching between isolated repo environments.

Core Features & Use Cases

  • Unified AI Assistant Session: Surfaces all agents, commands, skills, and hooks from every sub-repo into a single Claude Code or Codex session via automatically generated symlinks, so you never have to switch contexts between repos to access your custom AI tools.
  • Worktree-Based Multi-Repo Feature Development: Create synchronized feature branches across all your sub-repos with lightweight git worktrees, work on cross-repo features in one session, and clean up worktrees when the feature is merged.
  • Self-Sufficient Workspace Shell: The generated workspace is standalone and only tracks cross-repo glue files (bootstrap scripts, workspace config, symlinks) — sub-repo contents are gitignored, so the workspace never interferes with individual repo workflows.
  • Use Case: A developer working on a paired frontend (React) and backend (Node.js) repo can create a single workspace that exposes both repos' custom AI agents, create shared worktrees for a new authentication feature, and manage all work from one terminal session.

Quick Start

Use the virtual-workspace skill to create a unified parent workspace for your frontend and backend git repositories that combines all their Claude Code and Codex AI assistant configurations into a single shared session.

Frequently Asked Questions about virtual-workspace

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

FAQPage Schema
How do I manage Claude Code or Codex sessions across multiple git repositories?

You can unify multiple git repositories into a single AI coding assistant session by generating a shared workspace. This workspace automatically symlinks agents, commands, skills, and hooks from all sub-repos so you can interact with Claude Code or Codex without manually switching contexts between separate repository directories.

What is the best way to create synchronized feature branches across sibling repositories?

Synchronized feature branches across sibling repositories are created using lightweight git worktrees within a unified workspace. This approach allows you to manage cross-repo feature development in a single terminal session and easily remove the worktrees once the feature branches are merged.

Can I sync my custom AI assistant configurations across different projects?

Yes, you can sync custom AI assistant configurations across different projects by mirroring config files into a standalone workspace shell. The workspace generates symlinks to surface agents and hooks from every sub-repo, ensuring all custom tools are available in a single session without duplicating files.

Does the unified workspace track the contents of my individual git sub-repos?

No, the unified workspace does not track individual git sub-repo contents. The self-contained workspace shell only tracks cross-repo glue files like bootstrap scripts, symlinks, and workspace configuration, while automatically gitignoring sub-repo contents to prevent interference with individual repository workflows.

Do I need git installed to set up a multi-repo workspace for AI coding assistants?

Yes, git is required to set up a multi-repo workspace for AI coding assistants. The workspace shell relies on git to handle repository cloning, generate symlinks, and create synchronized worktrees for feature branch management across your sibling repositories.