lex-multirepo

What problem does it solve?

It solves the repeated setup cost of finding, cloning, and caching the correct sibling lex-fmt repositories when an agent needs to plan or analyze work that spans multiple repos.

Core Features & Use Cases

• Cross-repo bootstrapping into a shared cache: Standardizes cloning sibling lex-fmt repos into /tmp/lex-fmt so multi-repo sessions don’t re-discover paths every time.
• Correct handling of GitHub access limitations: Helps avoid MCP GitHub “Access denied” issues by using the intended bootstrapped repos plus gh for cross-repo operations.
• Targeted selection to reduce overhead: Supports cloning a minimal subset (or --all for audits) and optional shallow/full history tradeoffs for planning vs grep vs git-log needs.

Use it when a task explicitly names sibling repos, requires cross-repo analysis, or needs shared specs/config hosted in comms.
Avoid it when the task is confined to the rooted repo (including monorepo-internal work) or is only a generic “multi-file” keyword match.

Quick Start

Tell the agent: "Use lex-multirepo to clone the needed sibling lex-fmt repos into /tmp/lex-fmt using clone-lex-stack, then read the required files from /tmp/lex-fmt/<repo>/ for my cross-repo analysis."