Git Workflow and Versioning
addyosmani/agent-skills
Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.
Apply when committing, pushing, opening or updating a pull request, or closing out CI.
Install Commit PR
$ npx skills add ZaxbyHub/opencode-swarm --skill commit-pr -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ZaxbyHub/opencode-swarm commit-pr --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/.opencode/skills/commit-pr .claude/skills/commit-pr && 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 "commit-pr" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/commit-pr into .claude/skills/commit-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-pr", 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/.opencode/skills/commit-prType 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 commit-pr -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ZaxbyHub/opencode-swarm commit-pr --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/.opencode/skills/commit-pr .agents/skills/commit-pr && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "commit-pr" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/commit-pr into .agents/skills/commit-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-pr", 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 commit-pr -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ZaxbyHub/opencode-swarm commit-pr --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/.opencode/skills/commit-pr .cursor/skills/commit-pr && 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 "commit-pr" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/commit-pr into .cursor/skills/commit-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-pr", 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 .opencode/skills/commit-pr--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 commit-pr -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ZaxbyHub/opencode-swarm commit-pr --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/.opencode/skills/commit-pr .gemini/skills/commit-pr && 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 "commit-pr" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/commit-pr into .gemini/skills/commit-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-pr", 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 commit-prInstalls 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 commit-pr -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/.opencode/skills/commit-pr .github/skills/commit-pr && 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 "commit-pr" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/commit-pr into .github/skills/commit-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-pr", 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 commit-pr -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 commit-pr --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/.opencode/skills/commit-pr .opencode/skills/commit-pr && 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 "commit-pr" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/commit-pr into .opencode/skills/commit-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "commit-pr", 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
commit-pr- GitHub stars
- 488
- Token cost
- ~1.2k tokens
- SKILL.md length
- 675 words
- Files
- 1
- Skills in repo
- 91
- Repo updated
- First seen
- Licence
- MIT
At a glance
Apply when committing, pushing, opening or updating a pull request, or closing out CI.
- Works in 7 steps: Working-tree hygiene → Discover the project's checks → Verify before you push → …
- Tasks that involve Pull requests
- SKILL.md covers Graph-first evidence contract, Step 0 — Working-tree hygiene, Step 1 — Discover the… and Step 2 — Verify before you push, plus 4 more sections
- Calls git
What it does
Commit PR is an agent skill from ZaxbyHub/opencode-swarm. Apply when committing, pushing, opening or updating a pull request, or closing out CI. A portable, project-agnostic commit and PR workflow: verify before you push, write conventional commits and a clear PR body, and never commit generated or secret files.
Its SKILL.md is about 1.2k 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 Development, covering Pull requests and Commit messages. It works with Git. 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
- Tasks that involve Pull requests
- Tasks that involve Commit messages
Example prompts
- “/commit-pr”
Workflow steps
7 steps, taken from the step headings in SKILL.md.
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:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, 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 PR loads about 1.2k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 675 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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:32
tput, `node_modules`/`target`/`vendor`, `.env`,
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). 675 words, ~1,216 tokens.
Download SKILL.mdSave it as
.claude/skills/commit-pr/SKILL.md (or your agent's skills folder).- name
- commit-pr
- description
- Apply when committing, pushing, opening or updating a pull request, or closing out CI. A portable, project-agnostic commit and PR workflow: verify before you push, write conventional commits and a clear PR body, and never commit generated or secret files.
- audience
- swarm-plugin
- effort
- medium
Commit & PR Protocol (portable)
Graph-first evidence contract
Before publication, use repo_map diff_context and impact_cone as a final drift check, then verify the direct source, Git diff, and tests. Graph evidence is advisory only. If freshness is stale or inconclusive, confidence is low, source is missing, the language is unsupported/dynamic, the graph is absent, or an action fails, publication decisions rely on the direct evidence.
A project-agnostic workflow for landing a change safely. It makes no assumptions about the language, build tool, or hosting provider — discover each project's own conventions and follow them. Do every step in order.
If the repository ships its own commit/PR contract (a
CONTRIBUTING.md, a pull-request template, a contributor-guide file, or a project-specific commit-pr skill), that contract wins over this generic guidance. Read it first.
Step 0 — Working-tree hygiene
git statusandgit diff— know exactly what you are about to commit.- Confirm you are on a feature branch, not the default branch. If you are on
main/master, create a branch first. - Do not stage generated output, dependency directories, local caches, or
secrets (build/
distoutput,node_modules/target/vendor,.env, credentials, keys). If any are tracked or unignored, fix.gitignoreinstead of committing them.
Step 1 — Discover the project's checks
Find the project's own validation commands rather than guessing:
- A package manifest's script section (e.g.
package.jsonscripts,Makefiletargets,pyproject.toml,Cargo.toml,justfile,Taskfile). - CI workflow files under
.github/workflows/(or the provider's config) — these are the checks that must pass to merge.
Run the project's build, test, lint, type-check, and format checks — whatever exists. Pin tool versions to what the project declares so local results match CI. If a check fails, fix the cause; do not weaken, skip, or delete the check.
Step 2 — Verify before you push
Run the discovered checks and confirm they pass. Report the exact commands and their results — never claim a check passed without having run it. Passing tests mean the change is plausible, not automatically correct: make sure the change actually does what the task intended.
Step 3 — Commit
Write a clear, conventional commit message:
- Title:
<type>(<scope>): <summary>where<type>is one offeat,fix,perf,refactor,docs,test,build,ci,chore,revert. - Keep the title short and imperative; put detail in the body.
- One logical change per commit where practical.
Show full SKILL.md (296 more words)Show less
Step 4 — Push
- Identify the correct remote. If the repo has several remotes, push to the one the PR targets (the upstream you are contributing to), not an unrelated fork.
git push -u <remote> <branch>for a new branch.- If a push is rejected because you rebased, use
git push --force-with-lease— never a plain, unconditional force push.--force-with-leaserefuses to overwrite commits the remote gained since your last fetch, so it cannot silently clobber a teammate's work.
Step 5 — Open or update the PR
Search the repo for a PR template
(.github/PULL_REQUEST_TEMPLATE.md or .github/PULL_REQUEST_TEMPLATE/). If one
exists, fill in its sections. Otherwise write a body with at least:
- Summary — what changed and why.
- Test plan — the checks you ran and their results.
- A linking keyword (
Closes #<issue>) when the PR resolves an issue.
Use a PR title in the same conventional-commit form as your commit.
Before generating the PR body, check if .swarm/issue-reference.json exists. If it
does and contains a number field, auto-populate Closes #<number> as the first line
of the PR body. If the file does not exist, fall back to Closes #<issue-number>.
Step 6 — Close out CI
After the PR is open, watch its checks. If CI fails, read the logs, reproduce locally, fix the real cause, and push again. A PR is not done until its required checks are green and any review feedback is addressed. Do not merge over failing required checks or disable a check to go green.
If this session is running an issue trace (/swarm issue --trace), call
record_issue_publication (issue number, PR number, canonical PR URL, HEAD sha)
right after the PR is opened so the issue-trace workflow can reach its terminal
published state — without it the trace stays at publication_handoff and is NOT
considered resolved.
© 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 .opencode/skills/commit-pr of ZaxbyHub/opencode-swarm.
Open the folder on GitHubat commit 766e873
Compare with similar skills
Commit PR 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 |
|---|---|---|---|---|---|---|
| Commit PR this skillZaxbyHub/opencode-swarm | 488 | — | ~1.2k | Automated safety check: Notes | MIT | |
| Git Workflow and Versioningaddyosmani/agent-skills | 102k | 2 repos | ~3.5k | Automated safety check: Notes | MIT | |
| React Router Pull Request Creatorremix-run/react-router | 57k | — | ~2.5k | Automated safety check: Pass | MIT | |
| Verdaccio Pull Request Workflowverdaccio/verdaccio | 18k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Emoji Commit ConventionsbaptisteArno/typebot.io | 11k | — | ~424 | Automated safety check: Pass | Custom licence | |
| Draft Pull Request Creatorwordpress-mobile/WordPress-Android | 3.2k | — | ~881 | Automated safety check: Notes | GPL-2.0 |
Similar skills
React Router Pull Request Creator
remix-run/react-router
Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.
Verdaccio Pull Request Workflow
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
Emoji Commit Conventions
baptisteArno/typebot.io
Sets the repository's convention for commit messages and pull request titles: one emoji prefix for the main intent, a concise title and clean follow-up commits.
Draft Pull Request Creator
wordpress-mobile/WordPress-Android
Commits and pushes current changes, writes a pull request title and body from the branch history and template, and opens a draft PR on GitHub after you approve it.
Submit PR
tisfeng/Easydict
创建或复用当前 checkout 已提交变更的 GitHub PR，必要时推送任务分支。PR 审查使用 review-pr；仅本地提交使用 git-commit。
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 Commit PR
What does Commit PR do?
Apply when committing, pushing, opening or updating a pull request, or closing out CI. Commit PR is an agent skill from ZaxbyHub/opencode-swarm. Apply when committing, pushing, opening or updating a pull request, or closing out CI.
When should I use Commit PR?
Commit PR fits situations like: tasks that involve Pull requests; tasks that involve Commit messages.
How do I install Commit PR in Claude Code?
Run `npx skills add ZaxbyHub/opencode-swarm --skill commit-pr -a claude-code`. Or copy the skill folder (.opencode/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 PR in Codex?
Run `npx skills add ZaxbyHub/opencode-swarm --skill commit-pr -a codex`. Or copy the skill folder (.opencode/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 PR 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 PR need to run?
Going by SKILL.md and its folder, Commit PR needs the command-line tools its instructions call (git).
Does Commit PR access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Commit PR safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Commit PR use?
Commit PR 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 PR use?
About 1.2k tokens (SKILL.md is roughly 4.9k 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 PR?
Skills that share tags, products or a category with Commit PR: Git Workflow and Versioning (addyosmani/agent-skills, 102k stars), React Router Pull Request Creator (remix-run/react-router, 57k stars), Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars) and Emoji Commit Conventions (baptisteArno/typebot.io, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Commit PR?
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.