Skills github-multi-repo
📦

github-multi-repo

v1.0.0 Content revision r1 High Risk ⚙️ External commands🌐 Network access📁 Filesystem access🔑 Env variables

Coordinate Multi-Repository GitHub Workflows

Teams managing many repositories need consistent updates, tests, and pull requests across related projects. This skill provides structured GitHub workflow guidance for coordinated multi-repository changes.

Supports: Claude Codex Code(CC)
⚠️ 38 Poor

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "github-multi-repo" from https://skillstore.io/skills/dnyoussef-github-multi-repo.md and its manifest at https://skillstore.io/api/skills/dnyoussef-github-multi-repo/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/dnyoussef-github-multi-repo.md Signed manifest GET /api/skills/dnyoussef-github-multi-repo/manifest Signed lockfile GET /api/skills/dnyoussef-github-multi-repo/lockfile

Test it

Using "github-multi-repo". Find TypeScript services and suggest dependency alignment.

Expected outcome:

  • Repository discovery summary with candidate services and shared packages.
  • Dependency alignment plan with tests, branch strategy, and review checkpoints.
  • Risk notes for repositories that need manual inspection before updates.

Using "github-multi-repo". Standardize integration workflows across three repositories.

Expected outcome:

  • Workflow standardization proposal with target files and expected behavior.
  • Per-repository rollout order and validation steps.
  • Pull request checklist for reviewers and maintainers.

Using "github-multi-repo". Prepare a multi-repository security patch rollout.

Expected outcome:

  • Patch rollout plan with discovery, audit, test, and approval phases.
  • Repository status table described in plain language.
  • Rollback and communication steps for failed updates.

Security Audit

High Risk
v8 • 7/5/2026 Open versioned report

Most static detections are Markdown fences, inline code, or placeholder links and are false positives. Confirmed issues are the examples that direct an agent to run GitHub CLI, use predictable temporary paths, modify hidden configuration, and create pull requests across many repositories. No prompt injection was found, but the community skill needs safety gates for broad repository write operations.

1
Files scanned
875
Lines analyzed
42
Review items
0
False positives ignored

Confirmed security concerns (2)

High
SKILL.md:109-130SKILL.md:379-401SKILL.md:430-452
Unbounded Multi-Repository Write Automation
The skill describes cloning many repositories, running package updates, committing, pushing branches, and creating pull requests without an explicit approval gate or allowlist. This can cause broad unintended changes when an agent has organization permissions.
The cited workflows explicitly list repositories, clone them, run package commands, commit changes, push branches, and create pull requests. The risk is the broad write intent, not merely the shell syntax.
Medium
SKILL.md:155-158SKILL.md:257-259
Absolute Workspace Path Access in Examples
Examples instruct the agent to read and list absolute /workspaces/ruv-FANN paths. In another environment this can read outside the user project or fail unpredictably.
The absolute paths are visible in Read and LS examples and are not parameterized. They appear to be copied from a specific workspace, so legitimate use is possible but portability and boundary risk remain.
Capability review items (42)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

High
SKILL.md:111-114
Ruby/shell backtick execution
--jq '.[] | select(.name | test("-service$")) | .name' > /tmp/repos.txt`)
This command flow lists repositories, clones them into /tmp, runs npm commands, commits changes, pushes branches, and creates pull requests. That is high-impact automation when the agent has organization permissions.
High
SKILL.md:130-139
Ruby/shell backtick execution
done`)
This command flow lists repositories, clones them into /tmp, runs npm commands, commits changes, pushes branches, and creates pull requests. That is high-impact automation when the agent has organization permissions.
High
SKILL.md:401-402
Ruby/shell backtick execution
done`)
This loop installs packages, runs tests, commits, pushes, and opens pull requests across discovered repositories. It is a high-impact write path without an explicit approval gate in the example.
High
SKILL.md:452-453
Ruby/shell backtick execution
done`)
This patch flow can run npm audit fix, commit changes, push branches, and create pull requests. That is high-impact repository modification under agent credentials.
High
SKILL.md:114-130
Template literal with command substitution
Bash(`cat /tmp/repos.txt | while read -r repo; do
This command flow lists repositories, clones them into /tmp, runs npm commands, commits changes, pushes branches, and creates pull requests. That is high-impact automation when the agent has organization permissions.
High
SKILL.md:439-452
Template literal with command substitution
Bash(`for repo in /tmp/audit-*.json; do
This patch flow can run npm audit fix, commit changes, push branches, and create pull requests. That is high-impact repository modification under agent credentials.
High
SKILL.md:339
Hidden file access
path: `${repo}/.github/workflows/integration.yml`,
The example writes a .github workflow file that can change CI behavior across repositories. Hidden workflow changes are high-impact and require review.
Medium
SKILL.md:83-86
Ruby/shell backtick execution
--jq '.[] | select(.languages | keys | contains(["TypeScript"]))'`)
This line is part of a Bash-wrapped GitHub CLI discovery flow that enumerates repositories and decodes package metadata. The usage appears legitimate, but it still executes external commands and reads repository content.
Medium
SKILL.md:90-98
Ruby/shell backtick execution
done | jq -s '.'`)
This line is part of a Bash-wrapped GitHub CLI discovery flow that enumerates repositories and decodes package metadata. The usage appears legitimate, but it still executes external commands and reads repository content.
Medium
SKILL.md:162-165
Ruby/shell backtick execution
-f sha=$(gh api repos/:owner/:repo/git/refs/heads/main --jq '.object.sha')`)
This is part of a GitHub API write workflow that creates refs or updates package content using command substitution. It is intended automation, but it can modify repositories if run with valid credentials.
Medium
SKILL.md:169-181
Ruby/shell backtick execution
-f content="$(cat aligned-package.json | base64)"`)
This is part of a GitHub API write workflow that creates refs or updates package content using command substitution. It is intended automation, but it can modify repositories if run with valid credentials.
Medium
SKILL.md:189-192
Ruby/shell backtick execution
--jq '.content' | base64 -d > /tmp/claude-source.md`)
This documentation sync example reads repository content into /tmp and sends encoded content back through the GitHub API. The pattern is purposeful, but it performs external commands and repository writes.
Medium
SKILL.md:196-204
Ruby/shell backtick execution
-f content="$(cat /tmp/claude-source.md | base64)"`)
This documentation sync example reads repository content into /tmp and sends encoded content back through the GitHub API. The pattern is purposeful, but it performs external commands and repository writes.
Medium
SKILL.md:239-240
Ruby/shell backtick execution
- [x] Cross-package compatibility"`)
This line closes a Bash-wrapped gh pr create command that would create a pull request. The exact line is mostly PR body text, but it belongs to an external command block.
Medium
SKILL.md:266-278
Ruby/shell backtick execution
--order desc`)
This line is part of a Bash-wrapped gh search command that performs network repository discovery. It is read-only, but it still invokes external tooling outside the local skill.
Medium
SKILL.md:367-370
Ruby/shell backtick execution
--json number -q .number`))
This dependency update workflow creates GitHub issues and discovers repositories through nested shell commands. It is legitimate DevOps automation, but it relies on external command execution with organization scope.
Medium
SKILL.md:376-379
Ruby/shell backtick execution
done`))
This dependency update workflow creates GitHub issues and discovers repositories through nested shell commands. It is legitimate DevOps automation, but it relies on external command execution with organization scope.
Medium
SKILL.md:436-439
Ruby/shell backtick execution
done`)
This security scan example clones repositories and writes audit results into /tmp using shell commands. It is legitimate security work, but it runs external commands across many repositories.
Medium
SKILL.md:162
Shell command substitution
-f sha=$(gh api repos/:owner/:repo/git/refs/heads/main --jq '.object.sha')`)
This is part of a GitHub API write workflow that creates refs or updates package content using command substitution. It is intended automation, but it can modify repositories if run with valid credentials.
Medium
SKILL.md:169
Shell command substitution
-f content="$(cat aligned-package.json | base64)"`)
This is part of a GitHub API write workflow that creates refs or updates package content using command substitution. It is intended automation, but it can modify repositories if run with valid credentials.
Medium
SKILL.md:196
Shell command substitution
-f content="$(cat /tmp/claude-source.md | base64)"`)
This documentation sync example reads repository content into /tmp and sends encoded content back through the GitHub API. The pattern is purposeful, but it performs external commands and repository writes.
Medium
SKILL.md:363-367
Shell command substitution
TRACKING_ISSUE=$(Bash(`gh issue create \
This dependency update workflow creates GitHub issues and discovers repositories through nested shell commands. It is legitimate DevOps automation, but it relies on external command execution with organization scope.
Medium
SKILL.md:370-376
Shell command substitution
TS_REPOS=$(Bash(`gh repo list org --limit 100 --json name | \
This dependency update workflow creates GitHub issues and discovers repositories through nested shell commands. It is legitimate DevOps automation, but it relies on external command execution with organization scope.
Medium
SKILL.md:440
Shell command substitution
if [ $(jq '.vulnerabilities | length' $repo) -gt 0 ]; then
The command substitution parses audit file names and vulnerability counts inside an automated patch loop. It is not clearly malicious, but unquoted path-derived values make the shell workflow riskier.
Medium
SKILL.md:441
Shell command substitution
cd /tmp/$(basename $repo .json | sed 's/audit-//')
The command substitution parses audit file names and vulnerability counts inside an automated patch loop. It is not clearly malicious, but unquoted path-derived values make the shell workflow riskier.
Medium
SKILL.md:160-162
Template literal with command substitution
Bash(`gh api repos/:owner/:repo/git/refs \
This is part of a GitHub API write workflow that creates refs or updates package content using command substitution. It is intended automation, but it can modify repositories if run with valid credentials.
Medium
SKILL.md:165-169
Template literal with command substitution
Bash(`gh api repos/:owner/:repo/contents/package.json \
This is part of a GitHub API write workflow that creates refs or updates package content using command substitution. It is intended automation, but it can modify repositories if run with valid credentials.
Medium
SKILL.md:192-196
Template literal with command substitution
Bash(`gh api repos/:owner/:repo/contents/claude-code-flow/CLAUDE.md \
This documentation sync example reads repository content into /tmp and sends encoded content back through the GitHub API. The pattern is purposeful, but it performs external commands and repository writes.
Medium
SKILL.md:215
Hidden file access
path: "claude-code-flow/.claude/commands/github/github-modes.md",
The example writes a .claude command file through GitHub tooling. Hidden agent configuration can affect future automation and should be reviewed carefully.
Medium
SKILL.md:111
Temp directory access
--jq '.[] | select(.name | test("-service$")) | .name' > /tmp/repos.txt`)
The workflow uses predictable /tmp paths while cloning and modifying repositories. This is common in examples, but it can collide with existing files and should use isolated temporary directories.
Medium
SKILL.md:114
Temp directory access
Bash(`cat /tmp/repos.txt | while read -r repo; do
The workflow uses predictable /tmp paths while cloning and modifying repositories. This is common in examples, but it can collide with existing files and should use isolated temporary directories.
Medium
SKILL.md:115
Temp directory access
gh repo clone org/$repo /tmp/$repo -- --depth=1
The workflow uses predictable /tmp paths while cloning and modifying repositories. This is common in examples, but it can collide with existing files and should use isolated temporary directories.
Medium
SKILL.md:116
Temp directory access
cd /tmp/$repo
The workflow uses predictable /tmp paths while cloning and modifying repositories. This is common in examples, but it can collide with existing files and should use isolated temporary directories.
Medium
SKILL.md:189
Temp directory access
--jq '.content' | base64 -d > /tmp/claude-source.md`)
The documentation sync flow stores repository content in a fixed /tmp file before uploading it. The use is understandable, but fixed temporary paths can expose or overwrite content.
Medium
SKILL.md:196
Temp directory access
-f content="$(cat /tmp/claude-source.md | base64)"`)
The documentation sync flow stores repository content in a fixed /tmp file before uploading it. The use is understandable, but fixed temporary paths can expose or overwrite content.
Medium
SKILL.md:380
Temp directory access
gh repo clone org/$repo /tmp/$repo -- --depth=1
The organization-wide update loop clones repositories into predictable /tmp paths and changes directories into them. This creates filesystem and collision risk during broad automation.
Medium
SKILL.md:381
Temp directory access
cd /tmp/$repo
The organization-wide update loop clones repositories into predictable /tmp paths and changes directories into them. This creates filesystem and collision risk during broad automation.
Medium
SKILL.md:433
Temp directory access
gh repo clone org/$repo /tmp/$repo -- --depth=1
The security patch workflow clones repositories and writes audit data to predictable /tmp paths before applying fixes. It is legitimate, but broad temp directory use increases operational risk.
Medium
SKILL.md:434
Temp directory access
cd /tmp/$repo
The security patch workflow clones repositories and writes audit data to predictable /tmp paths before applying fixes. It is legitimate, but broad temp directory use increases operational risk.
Medium
SKILL.md:435
Temp directory access
npm audit --json > /tmp/audit-$repo.json
The security patch workflow clones repositories and writes audit data to predictable /tmp paths before applying fixes. It is legitimate, but broad temp directory use increases operational risk.
Medium
SKILL.md:439
Temp directory access
Bash(`for repo in /tmp/audit-*.json; do
The security patch workflow clones repositories and writes audit data to predictable /tmp paths before applying fixes. It is legitimate, but broad temp directory use increases operational risk.
Medium
SKILL.md:441
Temp directory access
cd /tmp/$(basename $repo .json | sed 's/audit-//')
The security patch workflow clones repositories and writes audit data to predictable /tmp paths before applying fixes. It is legitimate, but broad temp directory use increases operational risk.

Risk Factors

⚙️ External commands (120)
SKILL.md:42-54 SKILL.md:54-57 SKILL.md:57-63 SKILL.md:63-66 SKILL.md:66-72 SKILL.md:72-79 SKILL.md:79-81 SKILL.md:83-86 SKILL.md:90-98 SKILL.md:98-101 SKILL.md:101-110 SKILL.md:111-114 SKILL.md:130-139 SKILL.md:139-144 SKILL.md:144-160 SKILL.md:162-165 SKILL.md:169-181 SKILL.md:181-184 SKILL.md:184-188 SKILL.md:189-192 SKILL.md:196-204 SKILL.md:204-207 SKILL.md:207-227 SKILL.md:239-240 SKILL.md:240-245 SKILL.md:245-262 SKILL.md:266-278 SKILL.md:278-281 SKILL.md:281-327 SKILL.md:327-330 SKILL.md:330-339 SKILL.md:339-340 SKILL.md:349-354 SKILL.md:354-359 SKILL.md:359-363 SKILL.md:367-370 SKILL.md:376-379 SKILL.md:401-402 SKILL.md:402-405 SKILL.md:405-424 SKILL.md:424-427 SKILL.md:427-431 SKILL.md:436-439 SKILL.md:452-453 SKILL.md:453-458 SKILL.md:458-489 SKILL.md:489-492 SKILL.md:492-509 SKILL.md:509-514 SKILL.md:514-530 SKILL.md:530-533 SKILL.md:533-544 SKILL.md:544-549 SKILL.md:549-560 SKILL.md:560-563 SKILL.md:563-572 SKILL.md:572-575 SKILL.md:575-586 SKILL.md:586-591 SKILL.md:591-597 SKILL.md:597-600 SKILL.md:600-607 SKILL.md:607-610 SKILL.md:610-616 SKILL.md:616-621 SKILL.md:621-648 SKILL.md:648-651 SKILL.md:651-671 SKILL.md:671-676 SKILL.md:676-681 SKILL.md:681-684 SKILL.md:684-689 SKILL.md:689-692 SKILL.md:692-697 SKILL.md:697-732 SKILL.md:732-737 SKILL.md:737-740 SKILL.md:740-745 SKILL.md:745-748 SKILL.md:748-753 SKILL.md:753-758 SKILL.md:758-763 SKILL.md:763-766 SKILL.md:766-771 SKILL.md:771-774 SKILL.md:774-779 SKILL.md:779-784 SKILL.md:784-790 SKILL.md:790-793 SKILL.md:793-799 SKILL.md:799-802 SKILL.md:802-808 SKILL.md:808-813 SKILL.md:813-819 SKILL.md:819-822 SKILL.md:822-828 SKILL.md:828-853 SKILL.md:853-854 SKILL.md:854-855 SKILL.md:855-856 SKILL.md:856-859 SKILL.md:859-860 SKILL.md:860-861 SKILL.md:861-862 SKILL.md:862-868 SKILL.md:124 SKILL.md:162 SKILL.md:169 SKILL.md:196 SKILL.md:363-367 SKILL.md:370-376 SKILL.md:440 SKILL.md:441 SKILL.md:445 SKILL.md:114-130 SKILL.md:160-162 SKILL.md:165-169 SKILL.md:192-196 SKILL.md:359-370 SKILL.md:439-452
🌐 Network access (3)
SKILL.md:519 SKILL.md:866 SKILL.md:867
📁 Filesystem access (17)
SKILL.md:215 SKILL.md:339 SKILL.md:89 SKILL.md:372 SKILL.md:111 SKILL.md:114 SKILL.md:115 SKILL.md:116 SKILL.md:189 SKILL.md:196 SKILL.md:380 SKILL.md:381 SKILL.md:433 SKILL.md:434 SKILL.md:435 SKILL.md:439 SKILL.md:441
🔑 Env variables (2)
SKILL.md:520 SKILL.md:520
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/dnyoussef-github-multi-repo/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/dnyoussef-github-multi-repo/security.svg)](https://skillstore.io/skills/dnyoussef-github-multi-repo?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/dnyoussef-github-multi-repo?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/dnyoussef-github-multi-repo/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/dnyoussef-github-multi-repo.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

Claude Flow Team. (2026). github-multi-repo security audit report (audit version 8) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/dnyoussef-github-multi-repo/audits/8

BibTeX citation

@techreport{claude-flow-team-dnyoussef-github-multi-repo-2026, author = {Claude Flow Team}, title = {github-multi-repo security audit report (audit version 8)}, institution = {Skillstore}, year = {2026}, number = {8}, url = {https://skillstore.io/skills/dnyoussef-github-multi-repo/audits/8}, note = {Author version 1.0.0} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "github-multi-repo security audit report (audit version 8)" version: "1.0.0" type: report authors: - name: "Claude Flow Team" date-released: "2026-07-05" url: "https://skillstore.io/skills/dnyoussef-github-multi-repo/audits/8" identifiers: - type: other value: "skillstore:dnyoussef-github-multi-repo:audit:8" description: "Skillstore immutable audit report identifier"

Compare variants

2 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Higher Skillstore usage
ruvnet Recommended

ruvnet-github-multi-repo

Skillstore Score 38
Evidence Confidence Medium
Skillstore usage 9
Updated

2026-08-21

Claude Flow Team Current

dnyoussef-github-multi-repo

Skillstore Score 38
Evidence Confidence Medium
Skillstore usage 8
Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: Medium
55
Architecture
100
Maintainability
87
Content
70
Community
74
Spec Compliance

What You Can Build

Coordinate Dependency Updates

Plan and execute dependency changes across related services with tests and pull requests.

Standardize Repository Workflows

Align templates, workflow files, and documentation patterns across an engineering organization.

Monitor Multi-Repo Health

Review repository connectivity, dependency drift, and synchronization quality across teams.

Try These Prompts

Discover Related Repositories 
Use this skill to identify related GitHub repositories for my project. Summarize likely roles, dependencies, and next checks before running commands.
Plan a Dependency Sync 
Create a dependency synchronization plan for these repositories. Include version checks, test order, branch names, and pull request review steps.
Coordinate Documentation Updates 
Compare the documentation patterns across these repositories and propose a safe synchronization workflow. Do not push changes until I approve.
Run a Guarded Organization Update 
Design a guarded organization-wide update workflow. Use an allowlist, dry run, per-repository status, and explicit approval before cloning, pushing, or opening pull requests.

Best Practices

  • Start with a dry run and a small repository allowlist before any organization-wide change.
  • Require human approval before cloning repositories, installing packages, pushing branches, or creating pull requests.
  • Use isolated temporary directories, quoted variables, and cleanup steps for command examples.

Avoid

  • Do not run broad wildcard repository updates without an allowlist and review plan.
  • Do not copy placeholder owners, paths, or webhook URLs into production configuration.
  • Do not let generated workflow or hidden configuration changes bypass code review.

Frequently Asked Questions

What does this skill help automate?
It helps plan coordinated GitHub workflows across multiple repositories, including updates, tests, templates, and pull requests.
Does it require GitHub access?
Yes. The examples assume authenticated GitHub CLI or compatible GitHub tooling with repository permissions.
Can it make changes across an organization?
The examples show organization-wide workflows, but users should require allowlists, dry runs, and explicit approval.
Is it safe to run every command directly?
No. Commands that clone, install packages, push branches, or open pull requests need review before execution.
What tools does it mention?
It references claude-flow, ruv-swarm, GitHub CLI, npm, jq, and GitHub repository APIs.
Can it manage documentation synchronization?
Yes. It provides examples for synchronizing documentation files and tracking sync status across repositories.

Developer Details

License

MIT

Author version

v1.0.0

Skillstore revision

r1

Repository

https://github.com/DNYoussef/ai-chrome-extension/tree/main/.claude/skills/github-multi-repo

Ref

c579efd02184f1128d6741d16e6c8d951d7d4208

Maintenance freshness

7/20/2026

Usage

5 downloads · 213 views

File structure

📄 SKILL.md

More from Claude Flow Team

Related Skills

View all