multi-repo-git

Orchestrate cross-repository git operations across SEBT's four repositories.

10|1|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/codeforamerica/sebt-self-service-portal --skill multi-repo-git
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: multi-repo-git
Source: https://github.com/codeforamerica/sebt-self-service-portal/tree/main/.claude/skills/multi-repo-git
Command: npx skills add https://github.com/codeforamerica/sebt-self-service-portal --skill multi-repo-git

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating git operations across SEBT's four repositories is error-prone and slows down development when teams work in parallel on branches and repo state.

Core Features & Use Cases

  • Cross-repo orchestration: run common git commands like sync, branch, and status across all targeted repositories in parallel.
  • Deterministic operations: explicitly apply git -C paths to ensure commands affect the intended repo.
  • Use Case: when preparing a feature release, synchronize main branches, create feature branches across repos, and verify clean working trees in a single workflow.

Quick Start

Run the multi-repo-git sync across all SEBT repositories to align their main branches.

Frequently Asked Questions about multi-repo-git

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

FAQPage Schema
How do I run git operations across multiple repositories in parallel?▼

To run git operations across multiple repositories in parallel, you can orchestrate cross-repository commands that explicitly apply git -C paths to target each repository, ensuring deterministic syncing and branching across all targeted repos simultaneously.

What is the best way to synchronize main branches across several repositories?▼

Synchronizing main branches across several repositories requires coordinated git ops that execute parallel sync commands, explicitly targeting each repository path to ensure all main branches align correctly without manual, error-prone repository-by-repository updates.

How do I create feature branches across multiple git repositories at once?▼

Creating feature branches across multiple git repositories at once involves running a parallel branch creation operation that explicitly applies git -C paths to each targeted repository, ensuring the feature branch is deterministically created across all specified repos in a single workflow.

Can I check the working tree status of multiple repositories in a single workflow?▼

Checking the working tree status of multiple repositories in a single workflow is possible by running parallel status checks that explicitly target each repository via git -C paths, allowing you to verify clean states across all targeted repositories simultaneously.

Why does coordinating git operations across multiple repositories cause errors?▼

Coordinating git operations across multiple repositories causes errors because manual parallel work on branches and repo states is inherently error-prone, making automated cross-repo orchestration with deterministic git -C path targeting necessary to prevent misaligned branches and incorrect repository states.

Do I need any special dependencies to automate multi-repo git commands?▼

Automating multi-repo git commands does not require special dependencies, as it relies on standard Git tooling to execute deterministic commands, requiring only explicit git -C paths to ensure operations affect the intended targeted repositories.