Nushell
ccusage/ccusage
Guides ccusage Nushell scripts. An agent skill from ccusage/ccusage.
Operational patterns for fork PRs (head repo differs from base repo).
Install Fork PR Operations
$ npx skills add ZaxbyHub/opencode-swarm --skill fork-pr-operations -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ZaxbyHub/opencode-swarm fork-pr-operations --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ZaxbyHub/opencode-swarm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/fork-pr-operations .claude/skills/fork-pr-operations && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "fork-pr-operations" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.agents/skills/fork-pr-operations into .claude/skills/fork-pr-operations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fork-pr-operations", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ZaxbyHub/opencode-swarm/tree/main/.agents/skills/fork-pr-operationsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ZaxbyHub/opencode-swarm --skill fork-pr-operations -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ZaxbyHub/opencode-swarm fork-pr-operations --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ZaxbyHub/opencode-swarm.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/fork-pr-operations .agents/skills/fork-pr-operations && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "fork-pr-operations" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.agents/skills/fork-pr-operations into .agents/skills/fork-pr-operations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fork-pr-operations", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ZaxbyHub/opencode-swarm --skill fork-pr-operations -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ZaxbyHub/opencode-swarm fork-pr-operations --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ZaxbyHub/opencode-swarm.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/fork-pr-operations .cursor/skills/fork-pr-operations && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "fork-pr-operations" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.agents/skills/fork-pr-operations into .cursor/skills/fork-pr-operations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fork-pr-operations", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ZaxbyHub/opencode-swarm.git --path .agents/skills/fork-pr-operations--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ZaxbyHub/opencode-swarm --skill fork-pr-operations -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ZaxbyHub/opencode-swarm fork-pr-operations --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ZaxbyHub/opencode-swarm.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/fork-pr-operations .gemini/skills/fork-pr-operations && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "fork-pr-operations" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.agents/skills/fork-pr-operations into .gemini/skills/fork-pr-operations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fork-pr-operations", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ZaxbyHub/opencode-swarm fork-pr-operationsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ZaxbyHub/opencode-swarm --skill fork-pr-operations -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ZaxbyHub/opencode-swarm.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/fork-pr-operations .github/skills/fork-pr-operations && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "fork-pr-operations" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.agents/skills/fork-pr-operations into .github/skills/fork-pr-operations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fork-pr-operations", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ZaxbyHub/opencode-swarm --skill fork-pr-operations -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ZaxbyHub/opencode-swarm fork-pr-operations --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ZaxbyHub/opencode-swarm.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/fork-pr-operations .opencode/skills/fork-pr-operations && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "fork-pr-operations" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.agents/skills/fork-pr-operations into .opencode/skills/fork-pr-operations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fork-pr-operations", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
fork-pr-operations- GitHub stars
- 494
- Token cost
- ~1.4k tokens
- SKILL.md length
- 456 words
- Files
- 1
- Skills in repo
- 91
- Repo updated
- First seen
- Licence
- MIT
At a glance
Operational patterns for fork PRs (head repo differs from base repo).
- Works in 4 steps: Ignore APPROVE rounds from bots. A bot… → Scan for new findings only. Compare the… → Focus on human reviewer findings. Bot… → …
- DevOps & Cloud work in your project
- SKILL.md covers When to use this skill, Workflow approval after push, Remote naming conventions and Force-push protocol, plus 4 more sections
- Calls gh and git; reaches github.com
What it does
Fork PR Operations is an agent skill from ZaxbyHub/opencode-swarm. 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.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud. It works with GitHub Actions and GitHub. The repository describes itself as: Architect-centric agentic swarm plugin for OpenCode. Hub-and-spoke orchestration with SME consultation, code generation, and QA review. The licence is MIT.
When your agent uses it
- DevOps & Cloud work in your project
Example prompts
- “/fork-pr-operations”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Ignore APPROVE rounds from bots. A bot APPROVE after a trivial push adds no signal.
- Scan for new findings only. Compare the latest bot review against prior rounds to identify newly raised issues.
- Focus on human reviewer findings. Bot findings are advisory; human reviewer findings are binding.
- Do not attempt to silence the bot. The multi-round pattern is by design.
What it can do on your machine
Read from SKILL.md and the folder at commit b63a4bd. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
ghgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Fork PR Operations loads about 1.4k tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 456 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from ZaxbyHub/opencode-swarm at commit b63a4bd, republished under its MIT licence (© ZaxbyHub). 456 words, ~1,380 tokens.
Download SKILL.mdSave it as
.claude/skills/fork-pr-operations/SKILL.md (or your agent's skills folder).- name
- fork-pr-operations
- description
- 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.
- audience
- swarm-plugin
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
# 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>/approveRace condition: run not yet created
After pushing, there is a brief window (1-5 seconds) before GitHub creates the workflow run object. If you try to approve too quickly, the run won't exist yet. Retry with a short delay:
# Wait for run to appear, then approve
sleep 5
gh run list --repo <upstream-owner>/<upstream-repo> --branch <branch-name> --limit 1 --json databaseId,status --jq '.[0]'
# If status is "waiting", approve:
gh api -X POST repos/<upstream-owner>/<upstream-repo>/actions/runs/<databaseId>/approvePermission requirements
The gh api -X POST .../approve call requires actions: write permission on the base (upstream) repository. This typically means your GitHub token needs the repo or public_repo scope, and you must have write access to the upstream repo. Fork owners without upstream write access cannot approve workflow runs — only upstream maintainers can.
gh auth status
# Verify you have repo/public_repo scope and write access to the upstream repoRemote naming conventions
Standard remote setup for fork-based contributions:
# origin = your fork
git remote add origin https://github.com/<your-username>/<repo>.git
# upstream = canonical repository
git remote add upstream https://github.com/<canonical-owner>/<repo>.git
# Additional forks by owner name (if collaborating across forks)
git remote add <collaborator> https://github.com/<collaborator>/<repo>.gitForce-push protocol
Always use --force-with-lease, never bare --force:
# Safe: verifies remote tracking branch matches expected SHA
git push --force-with-lease origin <branch-name>
# DANGEROUS: overwrites any remote changes, including work by collaborators
git push --force origin <branch-name> # NEVER DO THIS--force-with-lease checks that the remote tracking branch matches your local expectation. If someone else pushed between your last fetch and your force-push, the lease check fails safely instead of destroying their work.
Show full SKILL.md (195 more words)Show less
Rebase workflow
To sync a fork PR branch with upstream/main:
# Fetch latest from upstream
git fetch upstream
# Rebase your branch onto upstream/main
git rebase upstream/main
# Resolve conflicts if any, then continue
git rebase --continue
# Force-push the rebased branch to your fork
git push --force-with-lease origin <branch-name>After rebase + force-push, the PR head SHA changes. All CI checks re-trigger (subject to workflow approval for fork PRs).
Stale CI verification
After a rebase or force-push, verify CI check data belongs to the current PR head:
# Get current PR head SHA
gh pr view <number> --repo <upstream-owner>/<upstream-repo> --json headRefOid --jq '.headRefOid'
# Check if CI checks match this SHA
gh pr checks <number> --repo <upstream-owner>/<upstream-repo> --json name,state,startedAt,completedAtIf check data references an older SHA, the checks are stale. Cancel obsolete runs only after confirming they are not the current head:
# Cancel a specific run (only if it's NOT the current head)
gh run cancel <run-id> --repo <upstream-owner>/<upstream-repo>Bot review multi-round awareness
Automated bot reviewers (e.g., hermes-pr-review) post a new review after every push. If you push N times, you get N bot reviews. This is expected behavior, not a bug.
Strategy
- Ignore APPROVE rounds from bots. A bot APPROVE after a trivial push adds no signal.
- Scan for new findings only. Compare the latest bot review against prior rounds to identify newly raised issues.
- Focus on human reviewer findings. Bot findings are advisory; human reviewer findings are binding.
- Do not attempt to silence the bot. The multi-round pattern is by design.
Cross-references
.claude/skills/commit-pr/SKILL.md— PR publication protocol, including--force-with-leaseguidance and remote check verification.opencode/skills/swarm-pr-feedback/SKILL.md— Feedback closure workflow for addressing review findings.agents/skills/subprocess-safety/SKILL.md— Subprocess safety forghCLI calls
© ZaxbyHub, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/fork-pr-operations of ZaxbyHub/opencode-swarm.
Open the folder on GitHubat commit b63a4bd
Compare with similar skills
Fork PR Operations next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Fork PR Operations this skillZaxbyHub/opencode-swarm | 494 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Nushellccusage/ccusage | 19k | — | ~938 | Automated safety check: Pass | Custom licence | |
| Make GitHub Actions Workflowdotnet/efcore | 15k | — | ~2.1k | Automated safety check: Pass | MIT | |
| AI News RadarLearnPrompt/ai-news-radar | 1.8k | — | ~2.5k | Automated safety check: Notes | MIT | |
| Clawsweeperopenclaw/openclaw | 392k | — | ~3k | Automated safety check: Pass | MIT | |
| ONNX Runtime CI Managementmicrosoft/onnxruntime | 22k | — | ~4.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Make GitHub Actions Workflow
dotnet/efcore
Create GitHub Actions workflows for CI, automation, or PR management.
AI News Radar
LearnPrompt/ai-news-radar
A skill your agent uses when working on AI News Radar, 24 小时 AI 更新雷达, AI 更新雷达, 伯乐Skill, or Scout Skill: finding high-signal AI/tech sources, adding RSS/OPML/GitHub feeds, checking source health…
Clawsweeper
openclaw/openclaw
A skill your agent uses for all ClawSweeper work: OpenClaw issue/PR sweep reports, repair jobs, cloud fix PRs, @clawsweeper maintainer mention commands, trusted ClawSweeper-reviewed…
- Official
ONNX Runtime CI Management
microsoft/onnxruntime
Triggers, re-runs and unblocks the CI checks on an ONNX Runtime pull request, after diagnosing whether a failure is transient or needs a code change.
CI Watchdog
latitude-dev/latitude-llm
Continuously monitor GitHub PR CI checks and automatically fix failures until all checks pass.
More from ZaxbyHub/opencode-swarm
All 91 skills in this repoCodebase Review Swarm
ZaxbyHub/opencode-swarm
Runs an evidence-gated, quote-grounded audit of a codebase for security, QA, accessibility, performance and more, and writes a verified report without changing source files.
Issue Tracer
ZaxbyHub/opencode-swarm
Drives a bug report from validation and root-cause tracing through a critic-reviewed plan, an approved minimal fix and a PR-ready closure, never merging without recorded human approval.
Commit and PR Publishing for Codex
ZaxbyHub/opencode-swarm
Codex adapter for opencode-swarm that governs commits, pushes, draft PRs, PR body updates and CI closeout, deferring to the repo's canonical commit-pr protocol.
Durable Session State
ZaxbyHub/opencode-swarm
Keeps plans, decisions, evidence and reviewer verdicts in small files so long multi-phase tasks survive context compaction and session resumes.
Swarm PR Feedback Closer
ZaxbyHub/opencode-swarm
Ingests existing pull request feedback such as review comments and CI failures, verifies each claim, fixes confirmed issues and reports closure status for every item.
Swarm PR Subscribe
ZaxbyHub/opencode-swarm
Monitor a pull request after creation and act autonomously on pushed PR activity.
Related
Works with
Categories
Questions about Fork PR Operations
What does Fork PR Operations do?
Operational patterns for fork PRs (head repo differs from base repo). Fork PR Operations is an agent skill from ZaxbyHub/opencode-swarm. Operational patterns for fork PRs (head repo differs from base repo).
When should I use Fork PR Operations?
Fork PR Operations fits situations like: devOps & Cloud work in your project.
How do I install Fork PR Operations in Claude Code?
Run `npx skills add ZaxbyHub/opencode-swarm --skill fork-pr-operations -a claude-code`. Or copy the skill folder (.agents/skills/fork-pr-operations in ZaxbyHub/opencode-swarm) into .claude/skills/fork-pr-operations in your project. Claude Code loads it when a task matches its description.
How do I install Fork PR Operations in Codex?
Run `npx skills add ZaxbyHub/opencode-swarm --skill fork-pr-operations -a codex`. Or copy the skill folder (.agents/skills/fork-pr-operations in ZaxbyHub/opencode-swarm) into .agents/skills/fork-pr-operations in your project. Codex loads it when a task matches its description.
Can I use Fork PR Operations in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ZaxbyHub/opencode-swarm --skill fork-pr-operations -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fork-pr-operations, .gemini/skills/fork-pr-operations, .github/skills/fork-pr-operations and .opencode/skills/fork-pr-operations in your project.
What does Fork PR Operations need to run?
Going by SKILL.md and its folder, Fork PR Operations needs the command-line tools its instructions call (gh and git).
Does Fork PR Operations access the network?
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Fork PR Operations safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Fork PR Operations use?
Fork PR Operations is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Fork PR Operations use?
About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Fork PR Operations?
Skills that share tags, products or a category with Fork PR Operations: Nushell (ccusage/ccusage, 19k stars), Make GitHub Actions Workflow (dotnet/efcore, 15k stars), AI News Radar (LearnPrompt/ai-news-radar, 1.8k stars) and Clawsweeper (openclaw/openclaw, 392k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Fork PR Operations?
ZaxbyHub (a GitHub organization) maintains it in ZaxbyHub/opencode-swarm, which has 494 GitHub stars. The repository holds 91 skills in this directory. The repository was last updated on October 10, 2026.
Source: ZaxbyHub/opencode-swarm on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.