Default output: return only the result, blockers, and required evidence. Omit preambles, process narration, repeated context, confidence scores, and follow-up offers. Use at most five bullets unless a required artifact or schema needs more.

Cross-Repo Refactor

Coordinate a refactor that spans multiple repos. The orchestrating session reads the change description, plans the per-repo edits, fans out subagents to make them, collects the results onto a single feature branch in each repo, and pushes for review. The branch-guard hook ships alongside this skill — it physically prevents pushing to main/master/develop or any pre-existing branch.

When to Use

• A refactor needs coordinated changes in 3+ repos (e.g., shared library bump + downstream consumer updates)
• The change is mechanical or systematic — no novel design decisions per repo
• You need the agent to do the legwork without supervision

When NOT to Use

• The change touches only one repo — just edit and PR normally
• Different repos need different design decisions — handle each one in its own session
• You haven't decided on the new shape yet — explore in one repo first; come back to fan out

How to Run