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.
End-to-end PR workflow for opencode-swarm. An agent skill from ZaxbyHub/opencode-swarm.
Install Contributing
$ npx skills add ZaxbyHub/opencode-swarm --skill contributing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ZaxbyHub/opencode-swarm contributing --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/contributing .claude/skills/contributing && 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 "contributing" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/contributing into .claude/skills/contributing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contributing", 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/contributingType 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 contributing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ZaxbyHub/opencode-swarm contributing --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/contributing .agents/skills/contributing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "contributing" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/contributing into .agents/skills/contributing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contributing", 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 contributing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ZaxbyHub/opencode-swarm contributing --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/contributing .cursor/skills/contributing && 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 "contributing" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/contributing into .cursor/skills/contributing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contributing", 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/contributing--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 contributing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ZaxbyHub/opencode-swarm contributing --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/contributing .gemini/skills/contributing && 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 "contributing" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/contributing into .gemini/skills/contributing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contributing", 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 contributingInstalls 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 contributing -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/contributing .github/skills/contributing && 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 "contributing" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/contributing into .github/skills/contributing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contributing", 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 contributing -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 contributing --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/contributing .opencode/skills/contributing && 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 "contributing" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/contributing into .opencode/skills/contributing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contributing", 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
contributing- GitHub stars
- 494
- Token cost
- ~1.7k tokens
- SKILL.md length
- 633 words
- Files
- 1
- Skills in repo
- 91
- Repo updated
- First seen
- Licence
- MIT
At a glance
End-to-end PR workflow for opencode-swarm. An agent skill from ZaxbyHub/opencode-swarm.
- Works in 8 steps: Branch Setup → Commit Message Format (Conventional… → Release Notes (MANDATORY — every… → …
- Tasks that involve Commit messages
- SKILL.md covers 1. Branch Setup, 2. Commit Message Format…, 3. Release Notes (MANDATORY —… and 4. Run All Checks Locally (5…, plus 5 more sections
- Calls bun, git and bunx
What it does
Contributing is an agent skill from ZaxbyHub/opencode-swarm. End-to-end PR workflow for opencode-swarm. Covers branch setup, conventional commits, mandatory release notes, 5-tier CI checks, and PR submission format. Load this skill before creating branches, commits, or pull requests.
Its SKILL.md is about 1.7k 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 Commit messages, Changelog and release notes and Pull requests. 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 Commit messages
- Tasks that involve Changelog and release notes
- Tasks that involve Pull requests
Example prompts
- “/contributing”
Workflow steps
8 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 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:
bungitbunxnpmgh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, bunx, npm and 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
Contributing loads about 1.7k tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 633 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). 633 words, ~1,653 tokens.
Download SKILL.mdSave it as
.claude/skills/contributing/SKILL.md (or your agent's skills folder).- name
- contributing
- description
- End-to-end PR workflow for opencode-swarm. Covers branch setup, conventional commits, mandatory release notes, 5-tier CI checks, and PR submission format. Load this skill before creating branches, commits, or pull requests.
Contributing to opencode-swarm
1. Branch Setup
git checkout main && git pull origin main
git checkout -b <type>/<short-description>
bun install --frozen-lockfileBranch naming: <type>/<short-description> (e.g. feat/add-retry-backoff, fix/plan-sync-race).
2. Commit Message Format (Conventional Commits)
Every commit MUST follow: <type>(<optional scope>): <description>
Rules:
- Description lowercase, no trailing period
- Scope optional but encouraged
| Type | Changelog section | Version bump |
|---|---|---|
feat | Features | minor |
fix | Bug Fixes | patch |
perf | Performance | patch |
revert | Reverts | patch |
docs | Documentation | none |
chore | — | none |
refactor | — | none |
test | — | none |
ci | — | none |
build | — | none |
Breaking changes: add BREAKING CHANGE: <description> footer or ! suffix on type (e.g. feat!:). Triggers major bump.
Valid examples:
feat(architect): add retry backoff to SME delegationfix(circuit-breaker): prevent race condition on concurrent invocationsrefactor(swarm): extract phase orchestration into dedicated module
Invalid (rejected by CI):
WIP,fix stuff,Update README,feat: Add feature.(trailing period),Feat:(uppercase)
3. Release Notes (MANDATORY — every user-visible PR, no exceptions)
⛔ Do NOT compute the next version. ⛔ Do NOT create docs/releases/vX.Y.Z.md. ⛔ Do NOT write to a shared docs/releases/unreleased.md. release-please owns the version; the release workflow aggregates fragments at release time.
- Choose a short, kebab-case slug describing your change. Pick one unlikely to collide with concurrent PRs.
- Create
docs/releases/pending/<your-slug>.md.
Include:
- What changed (grouped by theme)
- Why (bug report, feature request, hardening)
- Migration steps (if any)
- Breaking changes (if any)
- Known caveats
Use a descriptive heading (# <topic>), not a version prefix. Even one-line changes need a fragment explaining why it matters. Aggregation is done by scripts/release-notes-fragments.mjs via .github/workflows/release-and-publish.yml — each PR owning its own unique file is what eliminates the merge-conflict hotspot.
4. Run All Checks Locally (5 tiers, all must pass)
# Tier 1: Quality
bun run typecheck
bunx biome ci .
# Tier 2: Unit tests
bun test tests/unit --timeout 120000
# Tier 3: Integration tests
bun test tests/integration ./test --timeout 120000
# Tier 4: Security & adversarial
bun test tests/security --timeout 120000
bun test tests/adversarial --timeout 120000
# Tier 5: Build + smoke
bun run build
bun test tests/smoke --timeout 120000package-check CI failures: package-check validates the npm tarball (npm pack + tarball contents) and is the authoritative packaging gate. A failure is a source/build/package-manifest problem, not generated-file drift. dist/ is generated and NOT committed — do not stage it; run bun run build locally only when you need the bundle. There is no longer a committed-dist drift check.
If a pre-existing unrelated failure exists, note it in the PR description but do NOT skip other tiers.
5. Push and Open PR
git push -u origin <branch-name>PR title MUST be a valid conventional commit: <type>(<scope>): <description>
PR body template:
## Summary
- Bullet 1
- Bullet 2
## Test plan
- [ ] Tier 1 quality checks pass
- [ ] Unit tests pass
- [ ] Integration tests pass
- [ ] Security/adversarial tests pass
- [ ] Build + smoke tests pass6. Do NOT Manually Edit These Files
release-please manages these automatically:
package.jsonversion fieldCHANGELOG.md.release-please-manifest.json
Never replace the release PR body, create tags/releases manually, or edit these files.
Show full SKILL.md (262 more words)Show less
7. CI Checks
The protected main ruleset requires the exact contexts in the
required-check-contract.json
and its fresh external evidence.
This is the live required set, not a claim that every listed job or matrix cell
runs on every pull request.
| Live required context(s) | Validates |
|---|---|
quality | TypeScript compiles, Biome lint + format clean |
security | Security & adversarial tests pass |
unit (ubuntu-latest, 1) through unit (ubuntu-latest, 4) and unit-passed | Required Ubuntu shards and their aggregate; extra platform cells are event- or path-scoped |
package-check and integration | Package and integration checks pass |
smoke (ubuntu-latest), smoke (macos-latest), smoke (windows-latest) | Required platform package builds and smoke tests pass |
php-validation and rust-sandbox-runner | Language/build validation passes |
check-title and pr-standards | PR title and standards checks pass |
coverage | Merge-group-only union coverage gate |
release-owner-guard is a dependency helper for the required quality context,
not a standalone required context. check-duplicates is a non-required helper.
The local drift workflow includes pull_request, push to main, and
merge_group: checks_requested, but drift remains intended-only until ruleset
promotion; its pre-promotion divergence is a visible nonblocking notice. See
docs/ci-required-check-contract.md.
8. GitHub Actions SHA Pinning
All uses: in .github/workflows/ must be pinned to full 40-char SHA with version comment:
- uses: actions/checkout@93cb6efe18208431cddfb8368fd83d5badbf9bfd # v5.0.1Find SHA: gh api repos/{owner}/{repo}/git/ref/tags/{tag} --jq '.object.sha'
PR Checklist
- Branch created from latest
main - Every commit follows
<type>(<scope>): <description> - PR title follows same format
- No manual edits to
package.jsonversion,CHANGELOG.md, or.release-please-manifest.json -
docs/releases/pending/<unique-slug>.mdexists with release notes (NOT adocs/releases/vX.Y.Z.mdfile) - New tests in correct
tests/subdirectory - Tests updated for any changed behavior
- If modifying workflows, all
uses:are SHA-pinned - All 5 CI tiers pass locally
- PR description includes summary and test plan
© 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/contributing of ZaxbyHub/opencode-swarm.
Open the folder on GitHubat commit b63a4bd
Compare with similar skills
Contributing 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 |
|---|---|---|---|---|---|---|
| Contributing this skillZaxbyHub/opencode-swarm | 494 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Git Workflow and Versioningaddyosmani/agent-skills | 104k | 2 repos | ~3.5k | Automated safety check: Notes | MIT | |
| Verdaccio Pull Request Workflowverdaccio/verdaccio | 18k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Commit And PR Messagessuperplanehq/superplane | 7.7k | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| Plane Release Notes Generatormakeplane/plane | 61k | — | ~2.5k | Automated safety check: Pass | AGPL-3.0 | |
| PR Pushicebear0828/codex-proxy | 1.8k | — | ~2.2k | Automated safety check: Notes | Custom licence |
Similar skills
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.
Commit And PR Messages
superplanehq/superplane
Write Git commit messages and pull request titles/descriptions using the Chris Beams / Tim Pope conventions (subject/body split, ~50-char subject, imperative mood, why-not-how body) plus ASD-STE100…
Plane Release Notes Generator
makeplane/plane
Builds categorized release notes for a Plane release pull request from its commits and writes them into the PR description, for both the plane-cloud and plane-ee repos.
PR Push
icebear0828/codex-proxy
Package the current working changes into a standards-compliant codex-proxy pull request: branch hygiene, commit message linting, CHANGELOG prompt, conventional commit, push, and gh pr create against…
PR Push
icebear0828/codex-proxy
Package the current working changes into a standards-compliant codex-proxy pull request: branch hygiene, commit message linting, CHANGELOG prompt, conventional commit, push, and gh pr create against…
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
Categories
Questions about Contributing
What does Contributing do?
End-to-end PR workflow for opencode-swarm. An agent skill from ZaxbyHub/opencode-swarm. Contributing is an agent skill from ZaxbyHub/opencode-swarm. End-to-end PR workflow for opencode-swarm.
When should I use Contributing?
Contributing fits situations like: tasks that involve Commit messages; tasks that involve Changelog and release notes; tasks that involve Pull requests.
How do I install Contributing in Claude Code?
Run `npx skills add ZaxbyHub/opencode-swarm --skill contributing -a claude-code`. Or copy the skill folder (.opencode/contributing in ZaxbyHub/opencode-swarm) into .claude/skills/contributing in your project. Claude Code loads it when a task matches its description.
How do I install Contributing in Codex?
Run `npx skills add ZaxbyHub/opencode-swarm --skill contributing -a codex`. Or copy the skill folder (.opencode/contributing in ZaxbyHub/opencode-swarm) into .agents/skills/contributing in your project. Codex loads it when a task matches its description.
Can I use Contributing 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 contributing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/contributing, .gemini/skills/contributing, .github/skills/contributing and .opencode/skills/contributing in your project.
What does Contributing need to run?
Going by SKILL.md and its folder, Contributing needs the command-line tools its instructions call (bun, git, bunx, npm and gh).
Does Contributing access the network?
SKILL.md contains no URLs. Its commands use git, npm and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Contributing 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 Contributing use?
Contributing 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 Contributing use?
About 1.7k 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 Contributing?
Skills that share tags, products or a category with Contributing: Git Workflow and Versioning (addyosmani/agent-skills, 104k stars), Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars), Commit And PR Messages (superplanehq/superplane, 7.7k stars) and Plane Release Notes Generator (makeplane/plane, 61k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Contributing?
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.