One-click install
npx skills add https://github.com/arthur-debert/release --skill lex-multirepo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lex-multirepo
Source: https://github.com/arthur-debert/release/tree/main/skills/lex-multirepo
Command: npx skills add https://github.com/arthur-debert/release --skill lex-multirepo

SYSTEM DOCUMENTATION & REQUIREMENTS

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."

Frequently Asked Questions about lex-multirepo

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

FAQPage Schema
How do I bootstrap sibling repositories for cross-repo agent tasks?

Bootstrapping sibling repositories for cross-repo agent tasks requires cloning needed repos into a shared /tmp/lex-fmt cache using clone-lex-stack, enabling multi-repo sessions to access shared specs and code without re-discovering paths.

Why does GitHub MCP return access denied during cross-repo operations?

GitHub MCP access denied errors during cross-repo operations often occur when relying on rooted-repo-only access; using bootstrapped sibling repos from the /tmp/lex-fmt cache plus gh CLI helps avoid these GitHub access limitations.

When do I need to clone sibling repos for multi-repo analysis?

Cloning sibling repos for multi-repo analysis is needed when a task explicitly names sibling repos, requires cross-repo analysis, or needs shared specs/config hosted in comms, but should be avoided for rooted-repo-only or monorepo-internal work.

Can I clone a minimal subset of repos for cross-repo planning?

Yes, you can clone a minimal subset of sibling repos for cross-repo planning to reduce overhead, or use --all for audits, with optional shallow or full history tradeoffs depending on grep vs git-log needs.

What happens if clone-lex-stack is missing when bootstrapping repos?

If clone-lex-stack is missing when bootstrapping sibling repos, the lex-multirepo skill applies a clear fallback mechanism so cross-repo agent tasks can still proceed with shared specs and release-cascade config.