Skills when-managing-multiple-repos-use-github-multi-repo
📦
when-managing-multiple-repos-use-github-multi-repo
Content revision r1 High Risk ⚙️ External commands
Coordinate Multi-Repository GitHub Workflows
Multi-repository programs are difficult to change consistently across dependencies, CI, and releases. This skill gives Claude, Codex, and Claude Code a structured process for analysis, migration, enforcement, and synchronized delivery.
Supports: Claude Codex Code(CC)
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "when-managing-multiple-repos-use-github-multi-repo" from https://skillstore.io/skills/dnyoussef-when-managing-multiple-repos-use-github-multi-repo.md and its manifest at https://skillstore.io/api/skills/dnyoussef-when-managing-multiple-repos-use-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.
Test it
Using "when-managing-multiple-repos-use-github-multi-repo". Update a shared authentication API across five microservices.
Expected outcome:
- The skill identifies upstream and downstream repositories before changes begin.
- It proposes draft pull requests, integration tests, and merge order based on dependencies.
- It highlights rollback tags and release notes needed for a coordinated deployment.
Using "when-managing-multiple-repos-use-github-multi-repo". Move three packages from a monorepo into separate repositories.
Expected outcome:
- The skill outlines target repository boundaries and shared library strategy.
- It includes history preservation, dependency rewrites, CI setup, and validation gates.
- It separates planning tasks from repository write operations for review.
Using "when-managing-multiple-repos-use-github-multi-repo". Check whether service repositories follow the same architecture rules.
Expected outcome:
- The skill creates a compliance workflow with rules, scan steps, and remediation priorities.
- It groups violations by severity and assigns follow-up work by repository.
- It recommends continuous checks after the initial cleanup.
Security Audit
High Riskv10 • 7/9/2026 Open versioned report
The static Ruby backtick findings are false positives because they point to Markdown fences, inline identifiers, or prose. The semantic review found risk in unpinned npx execution and repeated instructions to run relative workspace scripts that perform writes. No prompt injection or data exfiltration language was found.
2
Files scanned
611
Lines analyzed
0
Review items
0
False positives ignored
Confirmed security concerns (2)
High
Unpinned External Package Execution
The skill instructs execution of npx claude-flow@alpha, which can fetch mutable package code during task execution. This creates supply-chain risk if a user or agent runs the command without verification.
The npx command is explicit and uses an alpha tag rather than a pinned version. Risk depends on runtime confirmation and trust in the external package.
High
Untrusted Relative Script Execution
The skill repeatedly directs agents to run relative bash scripts for cloning, pull requests, releases, repository creation, and automated fixes. The scanned skill contains only SKILL.md and multi-repo-process.dot, so matching workspace scripts could be executed instead.
The instructions contain multiple explicit relative bash script invocations. The file structure for this skill does not include those scripts, increasing workspace-confusion risk.
Risk Factors
⚙️ External commands (50)
SKILL.md:35-38 SKILL.md:38-42 SKILL.md:42-44 SKILL.md:44-46 SKILL.md:46-48 SKILL.md:48-62 SKILL.md:62-71 SKILL.md:71-75 SKILL.md:75-77 SKILL.md:77-82 SKILL.md:82-86 SKILL.md:86-89 SKILL.md:89-95 SKILL.md:95-109 SKILL.md:109-119 SKILL.md:119-144 SKILL.md:144-150 SKILL.md:150-163 SKILL.md:163-173 SKILL.md:173-180 SKILL.md:180-186 SKILL.md:186-200 SKILL.md:200-206 SKILL.md:206-212 SKILL.md:212-222 SKILL.md:222-236 SKILL.md:236-242 SKILL.md:242-252 SKILL.md:252-258 SKILL.md:258-264 SKILL.md:264-270 SKILL.md:270-277 SKILL.md:277-281 SKILL.md:281-294 SKILL.md:294-302 SKILL.md:302-315 SKILL.md:315-321 SKILL.md:321-327 SKILL.md:327-337 SKILL.md:337-347 SKILL.md:347-358 SKILL.md:358-370 SKILL.md:370-376 SKILL.md:376-382 SKILL.md:382-388 SKILL.md:388-394 SKILL.md:394-400 SKILL.md:400-405 SKILL.md:405-411 SKILL.md:411-416
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.
Copy report link
https://skillstore.io/skills/dnyoussef-when-managing-multiple-repos-use-github-multi-repo/audits/10?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/dnyoussef-when-managing-multiple-repos-use-github-multi-repo?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/dnyoussef-when-managing-multiple-repos-use-github-multi-repo?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/dnyoussef-when-managing-multiple-repos-use-github-multi-repo/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/dnyoussef-when-managing-multiple-repos-use-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
DNYoussef. (2026). when-managing-multiple-repos-use-github-multi-repo security audit report (audit version 10) [Author version unspecified]. Skillstore. https://skillstore.io/skills/dnyoussef-when-managing-multiple-repos-use-github-multi-repo/audits/10BibTeX citation
@techreport{dnyoussef-dnyoussef-when-managing-multiple-repos-use-github-multi-repo-2026,
author = {DNYoussef},
title = {when-managing-multiple-repos-use-github-multi-repo security audit report (audit version 10)},
institution = {Skillstore},
year = {2026},
number = {10},
url = {https://skillstore.io/skills/dnyoussef-when-managing-multiple-repos-use-github-multi-repo/audits/10},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "when-managing-multiple-repos-use-github-multi-repo security audit report (audit version 10)"
version: "unspecified"
type: report
authors:
- name: "DNYoussef"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/dnyoussef-when-managing-multiple-repos-use-github-multi-repo/audits/10"
identifiers:
- type: other
value: "skillstore:dnyoussef-when-managing-multiple-repos-use-github-multi-repo:audit:10"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: Medium 55
Architecture
85
Maintainability
87
Content
71
Community
83
Spec Compliance
What You Can Build
Propagate Shared API Changes
Plan and sequence updates when one service contract affects several dependent repositories.
Split a Monorepo Safely
Design target repositories, preserve history, update dependencies, and validate the cutover plan.
Enforce Architecture Standards
Scan related repositories for policy drift and create a coordinated remediation plan.
Try These Prompts
Map Repository Dependencies
Analyze these repositories and identify direct dependencies, shared packages, and likely update order. Return a short dependency map and review risks.
Plan a Cross-Repo Change
Create a coordinated change plan for this API update across the affected repositories. Include sequencing, tests, owners, draft pull requests, and rollback steps.
Design a Monorepo Split
Review this monorepo structure and propose target repositories. Include module boundaries, dependency changes, history preservation, CI changes, and validation gates.
Coordinate a Synchronized Release
Build a synchronized release plan for these repositories. Include dependency order, version strategy, integration tests, merge rules, release notes, and rollback criteria.
Best Practices
- Review every generated plan before any repository write operation.
- Run changes in dependency order and keep rollback tags for coordinated releases.
- Use dry runs and draft pull requests before merges or releases.
Avoid
- Do not run relative shell scripts from a workspace before reviewing their contents.
- Do not merge downstream repositories before shared dependencies are released.
- Do not let worker agents change repository architecture without coordinator review.
Frequently Asked Questions
What problem does this skill solve?
It helps plan coordinated work across related GitHub repositories, especially when dependencies and releases must stay aligned.
Does it create repository changes automatically?
It provides workflows that can lead to changes, but users should approve commands and review pull requests first.
Can it migrate a monorepo into several repositories?
Yes. It describes planning, repository creation, history preservation, dependency rewrites, and validation steps.
Which tools does it expect?
It references Claude Flow, Flow Nexus MCP tools, GitHub access, Graphviz, Git, and repository automation scripts.
Is it suitable for small teams?
Yes. The workflow supports two to five repositories and can scale to larger repository groups.
What should users review before running it?
Users should review repository access, external packages, shell scripts, write operations, and release permissions.
Developer Details
Author
DNYoussefLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
0519034dad657fb1f7706e0550e962beeda73fdf
Maintenance freshness
7/18/2026
Usage
4 downloads · 298 views
File structure