multi-repo plugins

by github.com/openshift-eng

Manage isolated git worktree workspaces for multi-repo development

by Lauri Gates

Workflow orchestration patterns for parallel agents, CI pipelines, preflight checks, and checkpoint-based refactoring. Addresses common friction in multi-branch operations, permission restrictions, and context limits.

by Matt Corbett

Centralized multi-repo, multi-person activity & project tracking. Aggregates commits, pull requests, and issues across many GitHub repositories from the GitHub API and rolls them up by person, by repo, and by cross-repo project — so a team working in sibling repos has one place to see who did what, and a supervisor gets a manage-the-team view no single-repo activity log can provide. Ships a stdlib-only collector (GitHub REST API → normalized activity JSON), a markdown report generator (weekly tracker + rolling activity roll-up + per-project status), a self-contained HTML dashboard generator, an offline config linter, a copy-in GitHub Action template for scheduled refresh, an on-demand /portfolio-refresh command, an optional hand-maintained narrative layer, skills, a scenarios bank, and a knowledge bank of decision trees. Secrets stay in env/secrets, never in config. Requires ravenclaude-core@>=0.7.0.

by anshss

Self-improving multi-agent harness that grinds your ticket backlog across every repo in your product — guarded auto-merge on green CI, and every resolved ticket writes a lesson into your git-tracked CLAUDE.md. Every ticket starts on a cheap tier and escalates once, on measured failure, instead of being predicted expensive up front; deterministic fixes skip the model entirely; and the lessons file evicts rather than accumulates, so always-on context stays a fixed budget.

by Matthew Badali

A small, honest virtual dev team: context-isolated agents, deterministic gates, file-backed work state. Optional Codex QA, optional Jira or ServiceDesk Plus, optional Obsidian Kanban tickets, optional Obsidian memory.

by Jeon Sumin

Multi-project worktree dev server launcher + dashboard. SessionStart hook attaches per-project subrepos (registry-driven).

by Roman

Multi-repo agent orchestration with ownership enforcement, structured communication, and compliance-ready audit trails

by Viraj Patel

Generate a repo's delivery pipeline for whichever CI system it uses — one /cicd:workflow skill that resolves the tool from config and reads that tool's reference. Tools always install through mise; multi-repo and monorepo layouts are both supported.

by Jordan Richlen

Deploy daily GitHub automation that curates a living, self-invalidating operating index (a 'fleet playbook') for a glob of repos — always pointing at the repos as the source of truth, never posing as it.

by Christian Attard

Where work happens. A run is one attempt at one work item, held outside every repository it changes.

by souliane

Personal code factory for multi-repo projects

by Oleksandr Ieremchuk

Cowork side of the delivery process: locate a feature's phase across repos, run the review gates, hand work to Claude Code, verify integration, author docs.

by juhyeon-cha

애자일 계층(스프린트→레일→스토리→마일스톤→태스크)으로 멀티 레포 개발을 자율 진행하는 에이전트 하네스 — 원장은 어댑터(github·beads·notion), 보완 스킬 triage(백로그 정리)·status(현황)