dotnet-techne-cross-repo-impact

# .NET Cross-Repo Impact Analysis Procedural recipe for reviewing a .NET pull request against a multi-repo microservice workspace: detect breaking changes, trace their blast radius across repo boundaries, check for a compatible downstream PR, and render a structured `cross-repo-impact.md` report. This skill is **procedural only**. It does not describe agent identity, default stance, or severity philosophy — those belong in the consuming agent's system prompt. This skill tells the agent *how* to run the analysis when invoked. ## Requirements - **Synopsis v1.6.0+** binary available, either: - as a long-running MCP daemon (preferred — fastest, combined multi-repo graph kept warm), or - as a CLI invoked per-run (one-shot mode, no daemon required). Use the companion `dotnet-techne-synopsis` skill to auto-download and detect the binary. - **git** on the PATH for diff inspection. - A code-host CLI on the PATH for compatible-PR search: - `gh` for GitHub (authenticated, repo read). - `glab` for GitLab (authenticated, MR read). - Others acceptable if the agent's harness provides an equivalent `searchOpenPrs` tool. - Read access to a **workspace root** that contains the PR repo AND every other repo in the fleet as peer directories (Synopsis discovers repos by `.git` markers under the root). ## When to use this skill Trigger this skill when a PR diff touches any of: - Public types, methods, records, or interfaces in an assembly referenced by other proje...