git-workspace

Discover child git repositories and register them as submodules or ignored directories.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/eavichay/mycli --skill git-workspace-eavichay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-workspace
Source: https://github.com/eavichay/mycli/tree/main/.cursor/skills/git-workspace
Command: npx skills add https://github.com/eavichay/mycli --skill git-workspace-eavichay

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill eliminates the manual overhead of managing multiple related repositories by automating the discovery and registration of child repositories as Git submodules.

Core Features & Use Cases

  • Automated Discovery: Scans the project root for child repositories and registers them as Git submodules.
  • Flexible Integration: Supports both submodule-based tracking for deep integration and ignore-only mode for simple project isolation.
  • Use Case: When setting up a new development environment with multiple microservices, use this skill to instantly link all local repositories to the main workspace without manual git commands.

Quick Start

Run the git-workspace skill to discover and register all child repositories in the current directory as submodules.

Frequently Asked Questions about git-workspace

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

FAQPage Schema
How do I automate multi-repo workspace coordination with git submodules?

Automating multi-repo workspace coordination involves scanning the project root to discover child repositories and registering them as Git submodules. This eliminates manual overhead by automatically linking local repositories to the main workspace without manual git commands.

What is the best way to manage multiple repositories as submodules in a development environment?

Managing multiple repositories as submodules is best handled by discovering child repositories and registering them for deep integration. This approach provides unified management of complex development environments with multiple independent codebases.

Do I need a clean working tree to register child repositories as submodules?

Yes, registering child repositories as submodules requires a clean working tree and valid remote origin URLs for all child repositories. These prerequisites ensure safe submodule registration without data loss or conflicts.

Can I isolate projects without tracking child repositories as submodules?

Yes, you can isolate projects without submodule tracking by using ignore-only mode. This mode registers child repositories as git-ignored directories instead of submodules for simple project isolation.

When should I not use submodule registration for multi-repository workspaces?

Submodule registration for multi-repository workspaces should not be used when child repositories lack valid remote origin URLs or have uncommitted changes. The process requires a clean working tree to ensure safe registration.