Verified:GitHub

multi-repo-coordinator

Name: multi-repo-coordinator
Availability: InStock
Author: OgenticAI

Coordinate feature development across multiple repositories with automated dependency resolution and integration checks.

1|Updated May 10, 2026

Search Tags:#integration #parallel execution #repository management #feature management #cross-repo coordination

Ready to run

npx skills add https://github.com/OgenticAI/ogentic-audit --skill multi-repo-coordinator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: multi-repo-coordinator
Source: https://github.com/OgenticAI/ogentic-audit/tree/main/.claude/skills/multi-repo-coordinator
Command: npx skills add https://github.com/OgenticAI/ogentic-audit --skill multi-repo-coordinator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires cross-repo-coordinator, feature-factory, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the complex process of coordinating and integrating features across multiple repositories, ensuring efficient and error-free collaboration.

Core Features & Use Cases

Cross-Repo Coordination: Manage and synchronize feature development across multiple repositories.
Automated Brief Slicing: Generate sub-briefs for each repository, detailing the specific work and API contracts.
Parallel Execution: Spawn feature-factory invocations in parallel where possible, optimizing workflow efficiency.
Integration Check: Perform an integration check to ensure API contracts align across repositories.
Use Case: When developing a feature that spans multiple repositories, this Skill ensures that all components are developed, tested, and integrated correctly, saving time and reducing errors.

Quick Start

Run the multi-repo-coordinator skill to coordinate feature development across repositories.

Frequently Asked Questions about multi-repo-coordinator

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

FAQPage Schema

How do I coordinate feature development across multiple repositories?▼

Coordinating feature development across multiple repositories requires orchestrating dependency resolution, brief slicing, parallel execution, and integration checks to ensure API contracts align across all components.

What is automated brief slicing in cross-repo coordination?▼

Automated brief slicing in cross-repo coordination generates sub-briefs for each repository, detailing the specific development work and API contracts required for each individual repository component.

Do I need cross-repo-coordinator and feature-factory to manage parallel execution?▼

Yes, managing parallel execution across repositories requires the cross-repo-coordinator agent and feature-factory invocations to spawn parallel tasks and optimize workflow efficiency.

What is the best way to integrate features spanning multiple repositories?▼

The best way to integrate features spanning multiple repositories is to perform an automated integration check ensuring API contracts align across repositories after parallel execution of feature-factory tasks.

When should I not use cross-repo feature coordination?▼

Cross-repo feature coordination is unnecessary for single-repository tasks, as the overhead of dependency resolution, brief slicing, and parallel execution orchestration is designed specifically for multi-repo feature integration.