Skip to content
TrustedSkillsbeta
Back to all skills

Github Multi Repo

Checked
ruvnet·vlatest·backend·MIT

Automates tasks across multiple GitHub repositories, streamlining deployments, code reviews, and dependency management.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add ruvnet/ruflo --skill github-multi-repo --full-depth -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

ruvnet

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned ruvnet/claude-flow at 49da6ecc44.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
3 files, 2,361 lines
Copies in repo
3 — all of them scanned
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

The github-multi-repo skill enables AI agents to manage, clone, and interact with multiple GitHub repositories simultaneously within a single workflow. It streamlines operations by allowing batch processing of codebases without requiring manual context switching between different repository URLs.

When to use it

  • Automating security audits across an entire organization's monorepo or microservices architecture.
  • Synchronizing dependency updates and patching vulnerabilities in dozens of related projects at once.
  • Generating standardized documentation or code analysis reports for a suite of connected repositories.
  • Performing bulk refactoring tasks where logic changes need to be applied consistently across multiple codebases.

Key capabilities

  • Simultaneous access to multiple repository contexts within one session.
  • Batch execution of commands (e.g., cloning, linting, testing) across specified repos.
  • Aggregated reporting of findings or status updates from all targeted repositories.
  • Efficient management of credentials and authentication scopes for various projects.

Example prompts

  • "Scan all repositories in my organization for hardcoded API keys and generate a summary report."
  • "Clone the last three updated repositories, run the linter on each, and list any failing tests."
  • "Apply the latest security patch to every repository that uses Express.js as a dependency."

Tips & gotchas

Ensure your AI agent has appropriate read/write permissions for all target repositories before initiating bulk operations. Be mindful of rate limits imposed by GitHub when performing high-volume actions across many repos in a single run.