github-multi-repo-1-cross-repo-swarm-initialization
Sub-skill of github-multi-repo: 1. Cross-Repo Swarm Initialization (+4).
Best use case
github-multi-repo-1-cross-repo-swarm-initialization is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of github-multi-repo: 1. Cross-Repo Swarm Initialization (+4).
Teams using github-multi-repo-1-cross-repo-swarm-initialization should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/1-cross-repo-swarm-initialization/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How github-multi-repo-1-cross-repo-swarm-initialization Compares
| Feature / Agent | github-multi-repo-1-cross-repo-swarm-initialization | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of github-multi-repo: 1. Cross-Repo Swarm Initialization (+4).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 1. Cross-Repo Swarm Initialization (+4)
## 1. Cross-Repo Swarm Initialization
```bash
# List organization repositories
REPOS=$(gh repo list org --limit 100 --json name,description,languages \
--jq '.[] | select(.name | test("frontend|backend|shared"))')
# Get repository details
REPO_DETAILS=$(echo "$REPOS" | jq -r '.name' | while read -r repo; do
gh api repos/org/$repo --jq '{name, default_branch, languages, topics}'
done | jq -s '.')
# Initialize swarm with repository context
npx ruv-swarm github multi-repo-init \
--repo-details "$REPO_DETAILS" \
--repos "org/frontend,org/backend,org/shared" \
--topology hierarchical \
--shared-memory \
--sync-strategy eventual
```
## 2. Repository Discovery
```bash
# Search organization repositories
REPOS=$(gh repo list my-organization --limit 100 \
--json name,description,languages,topics \
--jq '.[] | select(.languages | keys | contains(["TypeScript"]))')
# Analyze repository dependencies
DEPS=$(echo "$REPOS" | jq -r '.name' | while read -r repo; do
if gh api repos/my-organization/$repo/contents/package.json --jq '.content' 2>/dev/null; then
gh api repos/my-organization/$repo/contents/package.json \
--jq '.content' | base64 -d | jq '{name, dependencies, devDependencies}'
fi
done | jq -s '.')
echo "Found $(echo "$REPOS" | jq length) TypeScript repositories"
echo "Dependencies: $DEPS"
```
## 3. Synchronized Dependency Update
```bash
# Create tracking issue
TRACKING_ISSUE=$(gh issue create \
--repo org/main-repo \
--title "Dependency Update: typescript@5.0.0" \
--body "Tracking issue for updating TypeScript across all repositories" \
--label "dependencies,tracking" \
--json number -q .number)
# Get all repos with TypeScript
TS_REPOS=$(gh repo list org --limit 100 --json name | jq -r '.[].name' | \
while read -r repo; do
if gh api repos/org/$repo/contents/package.json 2>/dev/null | \
jq -r '.content' | base64 -d | grep -q '"typescript"'; then
echo "$repo"
fi
done)
# Update each repository
echo "$TS_REPOS" | while read -r repo; do
gh repo clone org/$repo /tmp/$repo -- --depth=1
cd /tmp/$repo
npm install --save-dev typescript@5.0.0
if npm test; then
git checkout -b update-typescript-5
git add package.json package-lock.json
git commit -m "chore: Update TypeScript to 5.0.0
Part of #$TRACKING_ISSUE"
git push origin HEAD
gh pr create \
--title "Update TypeScript to 5.0.0" \
--body "Updates TypeScript to version 5.0.0
Tracking: #$TRACKING_ISSUE" \
--label "dependencies"
else
gh issue comment $TRACKING_ISSUE \
--body "Failed to update $repo - tests failing"
fi
cd -
rm -rf /tmp/$repo
done
```
## 4. Initialize Multi-Repo Swarm
```javascript
// Initialize multi-repo swarm
// Store multi-repo state
action: "store",
key: "multi-repo/state",
value: JSON.stringify({
repositories: ["frontend", "backend", "shared"],
topology: "hierarchical",
syncStrategy: "eventual"
})
})
// Orchestrate synchronized operations
task: "Update dependencies across all TypeScript repositories",
strategy: "parallel",
priority: "high"
})
```
## 5. Security Patch Coordination
```bash
# Scan all repos for vulnerable dependency
VULN_REPOS=()
for repo in $(gh repo list org --limit 100 --json name -q '.[].name'); do
if gh api repos/org/$repo/contents/package.json 2>/dev/null | \
jq -r '.content' | base64 -d | grep -q '"lodash": "4.17.19"'; then
VULN_REPOS+=("$repo")
fi
done
echo "Found ${#VULN_REPOS[@]} repos with vulnerable lodash"
# Create security tracking issue
SECURITY_ISSUE=$(gh issue create \
--repo org/security-tracking \
--title "SECURITY: Update lodash to 4.17.21" \
--body "Critical security update for lodash CVE-XXXX
Affected repos:
$(printf '- %s\n' "${VULN_REPOS[@]}")" \
--label "security,critical")
# Patch each repo
for repo in "${VULN_REPOS[@]}"; do
gh repo clone org/$repo /tmp/$repo -- --depth=1
cd /tmp/$repo
npm install lodash@4.17.21
npm audit fix
git checkout -b security-lodash-update
git add package.json package-lock.json
git commit -m "security: Update lodash to 4.17.21
Fixes CVE-XXXX
Tracking: $SECURITY_ISSUE"
git push origin HEAD
gh pr create \
--title "SECURITY: Update lodash to 4.17.21" \
--body "Critical security update" \
--label "security,critical"
cd -
rm -rf /tmp/$repo
done
```Related Skills
interactive-report-generator
Generate interactive HTML reports with Plotly visualizations from data analysis results. Supports dashboards, charts, and professional styling.
data-validation-reporter
Generate interactive validation reports with quality scoring, missing data analysis, and type checking. Combines Pandas validation, Plotly visualization, and YAML configuration for comprehensive data quality reporting.
repo-ecosystem-hygiene
Interpret the daily read-only repo ecosystem hygiene audit and route remediation through approved workflows.
orcaflex-reporting-fixture-proof-pattern
Build and extend fixture-backed OrcaFlex reporting proof paths in digitalmodel using stable metadata baselines, normalized HTML snapshots, and reusable reporting test helpers.
repo-sync
Smart repository synchronization across workspace-hub ecosystem — diagnoses and fixes pull failures (detached HEAD, diverged branches, uncommitted changes)
repo-structure
Canonical source layout, test mirroring, root cleanliness, gitignore, docs classification, and committed artifact rules for all workspace-hub tier-1 repos. Consult before creating directories or files in any submodule.
repo-portfolio-steering
Generate a one-page portfolio steering report for workspace-hub. Use when the user invokes /repo-portfolio-steering, asks about harness vs engineering balance, wants a portfolio health check, or asks which repos to fund next. Reports on portfolio steering, GTM readiness, and provider activity balance.
repo-mission-portfolio-audit
Audit the workspace-hub repo portfolio to extract each repo's mission, identify documentation gaps, and prioritize a plan/approval sequence with explicit LLM-wiki weighting for future issue triage.
mixed-ops-vs-repo-fix-plan-boundary
Plan mixed operational-vs-repo remediation issues by proving live-state classification first, then only proposing code changes for confirmed repo-owned failure paths.
tax-filing-session-setup-with-github-tracking
Structured workflow for preparing and tracking a tax filing session using prepared documents, task checklist, and GitHub issue cross-referencing
tax-filing-session-setup-with-github-traceability
Structured workflow for setting up a multi-file tax filing session with GitHub issue tracking and prepared-file validation
repo-separation-for-sensitive-data
Architecture pattern for splitting confidential data and reusable algorithms across repos