---
name: songwhip-cross-repo
description: >-
  Use when analyzing, searching, or solutioning across multiple songwhip
  services. Triggers on: cross-repo code search ("where is X used across
  repos"), impact analysis ("if I change this API what breaks"), architecture
  questions ("how do services communicate"), multi-repo solutioning ("what
  needs to change across services to add this feature"), questions about shared
  packages (@theorchard/songwhip-*).
license: MIT
metadata:
  author: songwhip
  version: '1.1.0'
---

# Songwhip Cross-Repo Analysis

Discover, sync, and analyze all repositories containing `songwhip` in their name within the `theorchard` GitHub org. Combines the official `github` plugin (for repo discovery) with local shallow clones for deep cross-repo search, impact analysis, architecture mapping, and multi-service solutioning.

**This is a read-only analysis skill.** It never modifies files in other repos.

## Prerequisites

- The official **`github`** plugin is installed (provides the hosted GitHub MCP used for discovery). Install with `/plugin install github@claude-plugins-official`.
- `GITHUB_PERSONAL_ACCESS_TOKEN` is set in the environment (used by the `github` plugin's MCP and for authenticating git clones here).
- `git` and `jq` are available in PATH.

## When to Activate

- Questions about code spanning multiple songwhip services
- "Where is X used" or "what depends on X" in cross-service context
- Questions about shared packages (`@theorchard/songwhip-*`)
- Impact analysis requests across services
- Architectural questions about the songwhip platform

See `AGENTS.md` for the complete workflow and instructions.