fork-pr-operations SKILL.md skillA
This file is byte-identical to the first copy the registry indexed, one of 3 indexed copies. Same content hash, so the same checks give both the same grade.
fork-pr-operations from zaxbyhub/opencode-swarm is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add zaxbyhub/opencode-swarm/fork-pr-operations@git:20261012.097422cPins git:20261012.097422c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- zaxbyhub/opencode-swarm
- Path
.claude/skills/fork-pr-operations/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261012.097422c, committed Oct 12, 2026
- First version recorded
- Jul 10, 2026
- Size
- 5,541 bytes
- Repository stars
- 517
- License
- MIT
Operational patterns for fork PRs (head repo differs from base repo). Covers GitHub workflow approval after push, force-push protocol, remote naming conventions, stale CI verification, and bot review multi-round awareness. Load when working with fork PRs, cross-repo contributions, or workflow approval issues.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Fork PR Operations Fork PRs — where the head repository differs from the base repository — have a distinct operational lifecycle. GitHub treats them with stricter security defaults that require additional steps not needed for same-repo PRs. ## When to use this skill - You are pushing to a branch on a forked repository - CI checks are stuck in "waiting" status after a push - You need to rebase a fork PR branch against upstream/main - A bot reviewer posts after every push, creating multiple review rounds ## Workflow approval after push **Critical:** GitHub requires explicit workflow approval for fork PRs. After every push, CI jobs remain in "waiting" status until a user with write access to the base repository approves the workflow run. ### Approval command ```bash # List pending workflow runs for the PR gh run list --repo <upstream-owner>/<upstream-repo> --branch <branch-name> --limit 5 # Approve a specific run gh api -X POST repos/<upstream-owner>/<upstream-repo>/actions/runs/<run-id>/approve ``` ### Race condition: run not yet created …
Read the whole file at its exact version.
How to install
mdr add zaxbyhub/opencode-swarm/fork-pr-operations@sha256:09f3f9afb030d1b8The line at the top of this page pins the label git:20261012.097422c, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ery42pl5phg554a2)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Jul 10, 2026 and Oct 12, 2026, about one every 47 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261012.097422c latest | 2026-10-12 | 097422c | 5,541 B | A | view · diff |
| git:20260711.5972d3e | 2026-07-11 | 5972d3e | 5,529 B | A | view · diff |
| git:20260710.36020d6 | 2026-07-10 | 36020d6 | 5,506 B | A | view |
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 (5541 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
zaxbyhub/opencode-swarm · 517 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ery42pl5phg554a2 GET https://markdownregistry.com/api/v1/resolve?ref=zaxbyhub/opencode-swarm/fork-pr-operations GET https://markdownregistry.com/api/v1/blob/09f3f9afb030d1b8d69fc9a5fee81880bd409f97f8bc28692096913f0b63662e
Your AI assistant 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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from zaxbyhub/opencode-swarm
Every file in zaxbyhub/opencode-swarm