Cross-Repo Orchestration — Skill

Architectural note: This file covers scope inference, batch mutation strategy, fork/archive

handling, and rate limit budgeting. These are all cross-repo session concerns that must

be active together — you cannot infer scope without knowing how to handle forks, or apply

batch mutations without knowing the rate limit strategy. The single-repo module skills

(security, pr-management, etc.) are single-concept; this is the portfolio orchestrator

and is deliberately broader in scope.

Relationships: Loaded by commands/repo-manager.md when cross-repo mode is detected.

The nine module skills run per-repo within a cross-repo session; their findings are

aggregated here using the report template in repo-manager-assessment/SKILL.md.

If mutation strategy or scope inference logic changes here, update the design doc

(github-repo-manager-design.md §9.4–9.6) accordingly.

When This Skill Applies

• Owner asks about multiple repos ("check all my repos", "which repos need X")
• Owner asks a question scoped to a concern, not a repo ("any open PRs?", "security posture")