Skip to content
TrustedSkillsbeta
Back to all skills

Github Multi Repo

Checked
proffesor-for-testing·vlatest·backend·MIT

Helps with testing, GitHub as part of testing, debugging, and quality assurance workflows.

Repository

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 proffesor-for-testing/agentic-qe --skill github-multi-repo -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

proffesor-for-testing

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 proffesor-for-testing/agentic-qe at 124d8c735e.

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

Commit
124d8c735e
Manifest
.claude/skills/github-multi-repo/SKILL.md
Scanned
1 file, 783 lines
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

What it does

This skill enables AI agents to discover, clone, and test multiple GitHub repositories simultaneously. It automates the workflow of setting up a testing environment across various codebases without manual intervention for each repository.

When to use it

  • You need to validate changes or run tests against several related open-source projects at once.
  • Your team maintains a monorepo structure where dependencies span multiple distinct repositories.
  • You want to automate regression testing across a suite of microservices hosted on GitHub.
  • You are conducting security audits or dependency scans across an organization's public codebase.

Key capabilities

  • Automatically discovers and clones multiple repositories from GitHub based on provided criteria.
  • Sets up isolated testing environments for each discovered repository.
  • Executes test suites or validation scripts across the entire multi-repo landscape.
  • Aggregates results from all tested repositories into a unified report.

Example prompts

  • "Clone and run the unit tests for all repositories in my organization's GitHub organization."
  • "Set up a testing environment for these three specific repositories: repo-a, repo-b, and repo-c."
  • "Scan multiple GitHub repos for deprecated dependencies and generate a summary report."

Tips & gotchas

Ensure you have write access to the target repositories or use public ones, as cloning private repos requires proper authentication tokens. Limit the number of concurrent repositories to avoid overwhelming your agent's execution context or hitting rate limits on the GitHub API.