New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Commit and PR Publishing for Codex

by ZaxbyHub in 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.

MITAuto-check passedDevelopment

Install Commit and PR Publishing for Codex

skills CLI
$ npx skills add ZaxbyHub/opencode-swarm --skill commit-pr -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ZaxbyHub/opencode-swarm commit-pr --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ZaxbyHub/opencode-swarm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/commit-pr .claude/skills/commit-pr && rm -rf skills-src

Use ~/.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/

Facts

Skill name
commit-pr
GitHub stars
488
Token cost
~1.6k tokens
SKILL.md length
859 words
Files
2
Skills in repo
91
Repo updated
First seen
Licence
MIT

At a glance

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.

  • Works in 4 steps: AGENTS.md → docs/engineering-invariants.md → ../../../.claude/skills/commit-pr/SKILL.md → …
  • Pushing a branch and opening a draft PR for an issue assignment
  • SKILL.md covers Source Of Truth, Codex Execution Rules, Publish Modes and Required Follow-Through, plus 3 more sections
  • Calls gh and bun

What it does

This skill is the Codex-side adapter for publishing work in opencode-swarm, and it must be loaded before git push, gh pr create, gh pr edit or gh pr ready. It points to the canonical Claude skill at .claude/skills/commit-pr/SKILL.md, which has to be read in full before committing or opening a PR. If instructions conflict, AGENTS.md wins, then docs/engineering-invariants.md, then the canonical skill, then this file.

Execution rules: use the shell for git, gh, build, test and CI commands, apply_patch for manual edits and parallel reads for independent checks, never stage .Codex/ or IDE-local files, and never open a second PR when one exists for the branch. The modes are new-pr, pr-followup and closeout. For an existing PR, the agent inspects unresolved feedback, including review threads, requested changes, CI failures, mergeability and whether checks match the current head, then updates the existing body and verifies the PR still points at the pushed head after a force-push. PRs stay draft while checks are pending or caveats remain.

When your agent uses it

  • Pushing a branch and opening a draft PR for an issue assignment
  • Updating an existing PR body after validation results change
  • Marking a PR ready once the required checks are green
  • Addressing PR review feedback before closeout

Example prompts

  • “Push this branch and open a draft PR for the issue I just finished.”
  • “The PR already exists. Update its body with the new test results and check CI.”
  • “Mark the PR ready only if the required checks are green on the current head.”

Requirements

  • git and the GitHub CLI (gh)
  • A checkout of opencode-swarm

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. AGENTS.md
  2. docs/engineering-invariants.md
  3. ../../../.claude/skills/commit-pr/SKILL.md
  4. this file

What it can do on your machine

Read from SKILL.md and the folder at commit 766e873. 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:

    • gh
    • bun

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    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

Commit and PR Publishing for Codex loads about 1.6k tokens when it runs. Until then it costs about 99 tokens; SKILL.md has 859 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~99
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

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 766e873, republished under its MIT licence (© ZaxbyHub). 859 words, ~1,648 tokens.

Download SKILL.mdSave it as .claude/skills/commit-pr/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
commit-pr
description
Mandatory Codex/Copilot publication adapter for opencode-swarm. Use for every GitHub issue assignment that results in code changes, commits, pushes, draft PRs, PR body edits, PR readying, release notes, or CI closeout. Must be loaded before `git push`, `gh pr create`, `gh pr edit`, or `gh pr ready`. Routes to the single canonical source of truth at `.claude/skills/commit-pr/SKILL.md`.
audience
swarm-plugin

Commit & PR

Use this skill for Codex-side publication work in opencode-swarm.

Source Of Truth

Read and follow ../../../.claude/skills/commit-pr/SKILL.md in full before committing, pushing, opening, or updating a PR.

That Claude skill remains the repository's canonical publish protocol. This Codex-native skill is the adapter layer: it tells Codex which tools to use, how to handle existing PRs, and how to finish the post-open lifecycle without drifting from the repo contract.

If instructions conflict:

  1. AGENTS.md
  2. docs/engineering-invariants.md
  3. ../../../.claude/skills/commit-pr/SKILL.md
  4. this file

Codex Execution Rules

  • Use the available shell execution tool for git, gh, build, test, and CI commands.
  • Use apply_patch for manual file edits.
  • Use the runtime's parallel-execution capability for independent reads, status checks, and non-conflicting repo inspections.
  • Do not stage .Codex/, IDE-local files, or unrelated worktree changes.
  • Do not open a second PR when one already exists for the branch. Update the existing PR instead.

Publish Modes

Infer the mode from the user request and branch state:

  • new-pr: branch is ready to publish and no PR exists yet
  • pr-followup: a PR already exists and you are addressing review feedback or syncing validation
  • closeout: a PR already exists and you are updating body text, waiting on CI, marking ready, or confirming merge prerequisites

Required Follow-Through

Existing PR updates

If the branch already has a PR:

  • inspect unresolved PR feedback surfaces before updating or readying the PR: review threads/comments, requested-changes reviews, CI/check failures, mergeability/conflicts, and whether check data belongs to the current head SHA
  • update the existing PR body instead of creating a new PR
  • refresh ## Summary, ## Invariant audit, and ## Test plan when validation counts, caveats, or evidence changed
  • verify the PR still points at the pushed branch head after any force-push
  • use $swarm-pr-feedback when feedback needs fixes before closeout
Draft vs ready

Default behavior:

  • open or keep the PR as draft while follow-up edits are still expected, required checks are pending, or known caveats still need explanation
  • mark the PR ready only after the body is current and required remote checks are green

If the user explicitly asks for a ready PR sooner, obey that request and document any remaining CI state clearly.

Remote checks are authoritative

When the user asks to open, ship, ready, or close out a PR:

  1. inspect remote checks with gh pr view <n> --json statusCheckRollup,... or gh pr checks <n>
  2. verify check data belongs to the current headRefOid after every follow-up push
  3. if a required job is cancelled and downstream jobs are skipped, inspect the run and rerun failed/cancelled jobs
  4. if an obsolete older-head run is already failed or still consuming concurrency, inspect it before cancellation and cancel only when it is no longer the PR head under validation
  5. wait for required checks to finish when practical
  6. after conflict resolution, verify GitHub reports both mergeable: MERGEABLE and mergeStateStatus: CLEAN; local conflict-marker cleanup is not enough, and branch drift must appear in the closure ledger when it affected the PR
  7. when gh pr checks looks stale, inspect the workflow run directly with gh run view <run-id> --json headSha,status,conclusion,jobs,url, and keep watching downstream integration/smoke jobs after unit jobs pass
  8. if you edit the PR body after checks are green, expect PR Standards/title checks to rerun and re-check before calling the PR green
  9. do not call the PR merge-ready while a required check is cancelled, skipped, in_progress, or otherwise non-green unless the user explicitly accepts that state
Show full SKILL.md (291 more words)Show less

Recommended commands:

powershell
gh pr view <number> --json body,headRefName,headRefOid,isDraft,mergeable,mergeStateStatus,state,statusCheckRollup,url
gh pr checks <number> --watch --fail-fast
gh run view <run-id> --json headSha,status,conclusion,jobs,url
gh run rerun <run-id> --failed

dist/ is generated output and is not committed (#1047); do not stage it and there is no dist-check drift gate. If package-check fails, inspect the CI log: it is a source / build / package.json#files problem (an incomplete or unbuildable tarball), not generated-file drift. Fix the source or manifest and rerun bun run package:smoke locally.

After a forced install on Windows, EPERM while reading refreshed node_modules is usually host friction; rerun the exact focused command with approved access before treating it as a code failure.

Issue comment requirement

If the PR closes an issue:

  • confirm the issue comment exists with the PR link, what changed, how to use it, and migration notes
  • if the PR merged before the comment was posted, add the missing issue comment immediately

Working Pattern

  1. Read AGENTS.md, docs/engineering-invariants.md as needed, and the canonical Claude commit-pr skill.
  2. Run the required local validation from the canonical skill.
  3. Stage only intended files.
  4. Create or update the PR.
  5. Refresh PR body text if the branch changed after review feedback.
  6. Watch remote checks to a useful conclusion when the user asked for publication or closeout.
  7. Verify issue comments, ready/draft state, and merge-readiness claims before finishing.

Clean-Main And CI Reality Checks

When local validation is noisy or host-limited:

  • compare suspicious failures against a clean origin/main worktree before blaming the branch
  • document proven pre-existing failures in the PR body
  • use remote CI as the cross-platform source of truth for merge-readiness

Final Sanity Check

  • one branch, one PR
  • PR head matches pushed HEAD
  • PR body matches current validation evidence
  • issue comment exists when the PR closes an issue
  • draft or ready state matches user intent
  • required remote checks are green, or any remaining non-green state is explicitly explained

© 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

SKILL.md and 1 other file in .agents/skills/commit-pr of ZaxbyHub/opencode-swarm.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 766e873

Compare with similar skills

Commit and PR Publishing for Codex 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.

Commit and PR Publishing for Codex compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Commit and PR Publishing for Codex this skillZaxbyHub/opencode-swarm488—~1.6kAutomated safety check: PassMIT
ZCF Release AutomationUfoMiao/zcf6.1k—~3.4kAutomated safety check: PassMIT
WooCommerce Draft PR Creatorwoocommerce/woocommerce11k—~1.1kAutomated safety check: PassCustom licence
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Release Bumpjamiepine/voicebox57k—~1.1kAutomated safety check: PassMIT

Similar skills

  • ZCF Release Automation

    UfoMiao/zcf

    Automates a version release with changesets: analyzes code changes, writes a bilingual CHANGELOG, bumps the version and commits through a release branch and pull request.

    6.1k GitHub stars~3.4k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • WooCommerce Draft PR Creator

    woocommerce/woocommerce

    Opens a concise draft pull request for the current branch, working out change type, base branch, title and body from the commits and diff.

    11k GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check passed

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • Create Pull Request

    cline/cline

    Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

  • Release Bump

    jamiepine/voicebox

    Ends a release cycle by moving the Unreleased changelog notes under a dated version heading, bumping version files with bumpversion and tagging the commit.

    57k GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check passed

  • Creating Description For Gh PR

    redis/jedis

    Official

    Generate a clear, concise GitHub PR title and description from the diff between two local git branches, and save it to prDescription.md in the repo root.

    12k GitHub stars~838 tokensUpdated today
    DevelopmentAuto-check passed

More from ZaxbyHub/opencode-swarm

All 91 skills in this repo

  • Codebase 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.

    488 GitHub stars~2.8k tokensUpdated today
    Auto-check passed

  • 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.

    488 GitHub stars~4.4k tokensUpdated today
    Auto-check passed

  • 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.

    488 GitHub stars~896 tokensUpdated today
    Auto-check passed

  • 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.

    488 GitHub stars~14k tokensUpdated today
    Auto-check passed

  • Swarm PR Subscribe

    ZaxbyHub/opencode-swarm

    Monitor a pull request after creation and act autonomously on pushed PR activity.

    488 GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Bundle Safety

    ZaxbyHub/opencode-swarm

    Bundle transform safety — minification variant selection, consumer-constraint verification, identifier preservation, and namespace re-export coverage for build output.

    488 GitHub stars~2.3k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Commit and PR Publishing for Codex

What does Commit and PR Publishing for Codex do?

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. This skill is the Codex-side adapter for publishing work in opencode-swarm, and it must be loaded before git push, gh pr create, gh pr edit or gh pr ready.md, which has to be read in full before committing or opening a PR.

When should I use Commit and PR Publishing for Codex?

Commit and PR Publishing for Codex fits situations like: pushing a branch and opening a draft PR for an issue assignment; updating an existing PR body after validation results change; marking a PR ready once the required checks are green; addressing PR review feedback before closeout.

How do I install Commit and PR Publishing for Codex in Claude Code?

Run `npx skills add ZaxbyHub/opencode-swarm --skill commit-pr -a claude-code`. Or copy the skill folder (.agents/skills/commit-pr in ZaxbyHub/opencode-swarm) into .claude/skills/commit-pr in your project. Claude Code loads it when a task matches its description.

How do I install Commit and PR Publishing for Codex in Codex?

Run `npx skills add ZaxbyHub/opencode-swarm --skill commit-pr -a codex`. Or copy the skill folder (.agents/skills/commit-pr in ZaxbyHub/opencode-swarm) into .agents/skills/commit-pr in your project. Codex loads it when a task matches its description.

Can I use Commit and PR Publishing for Codex 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 commit-pr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/commit-pr, .gemini/skills/commit-pr, .github/skills/commit-pr and .opencode/skills/commit-pr in your project.

What does Commit and PR Publishing for Codex need to run?

Going by SKILL.md and its folder, Commit and PR Publishing for Codex needs the command-line tools its instructions call (gh and bun). Our summary lists: git and the GitHub CLI (gh); A checkout of opencode-swarm.

Does Commit and PR Publishing for Codex access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Commit and PR Publishing for Codex 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 Commit and PR Publishing for Codex use?

Commit and PR Publishing for Codex 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 Commit and PR Publishing for Codex use?

About 1.6k tokens (SKILL.md is roughly 6.6k 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 Commit and PR Publishing for Codex?

Skills that share tags, products or a category with Commit and PR Publishing for Codex: ZCF Release Automation (UfoMiao/zcf, 6.1k stars), WooCommerce Draft PR Creator (woocommerce/woocommerce, 11k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Create Pull Request (cline/cline, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Commit and PR Publishing for Codex?

ZaxbyHub (a GitHub organization) maintains it in ZaxbyHub/opencode-swarm, which has 488 GitHub stars. The repository holds 91 skills in this directory. The repository was last updated on October 7, 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.