pr-all-repos skillA
pr-all-repos is agent-read markdown (skill) from raffertyuy/repo-of-repos: Create PRs in all sub-repos with uncommitted branches, then link them as siblings.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified before it reaches your agent: the main file against the SHA-256 recorded here, the others against the git hashes of its source commit. The deterministic audit below grades the latest version, and the same checks always give the same file the same grade.
What the file says
# PR All Repos
Create pull requests across all sub-repos that have branches ready for review, then cross-link them as sibling PRs.
## Prerequisites
- `gh` CLI must be authenticated (`gh auth status`)
- Each sub-repo must have a remote configured
## Order of Operations
1. **Scan** — identify repos with PR-ready branches
2. **Create PRs** — open a PR in each qualifying repo
3. **Cross-link** — update each PR description with sibling PR URLs
## Step 1: Scan
For each directory in `repos/*/` that is a git repository:
1. Check the current branch: `git -C repos/<name> branch --show-current`
2. **Skip** if on the default branch (main/master) — nothing to PR
3. Check if a PR already exists for this branch: `gh pr view --repo <remote> --json url 2>/dev/null`
4. **Skip** if a PR already exists — but record its URL for cross-linking
5. Check if the branch has been pushed: `git -C repos/<name> log @{u}..HEAD 2>/dev/null`
6. If unpushed commits exist, push first: `git -C repos/<name> push -u origin <branch>`
Collect the list of repos that need new PRs and repos that already have PRs.
## Step 2: Create PRs
For each repo that needs a new PR:
1. `cd` into the repo directory
…Read the whole file at its exact version.
How to install
mdr add raffertyuy/repo-of-repos/pr-all-repos@git:20260723.1db5b32mdr add raffertyuy/repo-of-repos/pr-all-repos@sha256:2ebe4152d4ba17f2Pin to a label to follow the author's releases, or to a sha256 for exact bytes. Either way the resolved hash is written to mdr.lock, and mdr install fetches those bytes again and checks them, so it installs them exactly or fails.
[](https://markdownregistry.com/a/art_rgseqp3kdzdmxhx2)
2 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3308 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
raffertyuy/repo-of-repos · 12 stars · license MIT · pushed 2026-09-25 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_rgseqp3kdzdmxhx2 GET https://markdownregistry.com/api/v1/resolve?ref=raffertyuy/repo-of-repos/pr-all-repos GET https://markdownregistry.com/api/v1/blob/2ebe4152d4ba17f273c9b3c029267716d248be16f0136e99a2a13b01f849a248
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from raffertyuy/repo-of-repos
Every file in raffertyuy/repo-of-repos