skills.rest
ZaxbyHub
ZaxbyHubOFFICIAL
Explore all skills by this author →
GitHub

contributing

Enforces commit formatting, PR title standards, and release notes for opencode-swarm contributions.

437|45|Updated Jan 27, 2026
Search Tags:#contributing#git-workflow#pull-request#release-notes#conventional-commits#ci-checks#opencode-swarm
One-click install
npx skills add https://github.com/ZaxbyHub/opencode-swarm --skill contributing-zaxbyhub
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: contributing
Source: https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/contributing
Command: npx skills add https://github.com/ZaxbyHub/opencode-swarm --skill contributing-zaxbyhub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the friction and inconsistency of contributing to the opencode-swarm project, ensuring all pull requests meet project standards, pass CI checks, and follow required workflows without manual guesswork.

Core Features & Use Cases

  • Standardized Branch & Commit Workflow: Enforces consistent branch naming and conventional commit formats to keep the project history clean and compliant.
  • Mandatory Release Notes & CI Validation: Requires unique release note fragments and guides you through running all 5 tiers of local checks to avoid CI failures on first submission.
  • Use Case: If you are contributing a bug fix, feature, or documentation update to opencode-swarm, this Skill walks you through every step from branch creation to PR submission to ensure your changes are accepted without rework.

Quick Start

Use the contributing skill to guide you through creating a standards-compliant pull request for your opencode-swarm code change.

Frequently Asked Questions about contributing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I submit a pull request to the opencode-swarm repository?▼

Submitting an opencode-swarm pull request requires following a standardized git workflow enforcing conventional commit formatting, mandatory release note fragments, and a 5-tier local CI validation before PR submission.

What is conventional commit formatting for open source contributions?▼

Conventional commit formatting is a standardized commit message structure enforced by the opencode-swarm project to keep version history clean, compliant, and easily parseable for generating release notes.

Why does my opencode-swarm pull request fail CI checks?▼

Your opencode-swarm pull request fails CI checks when contributions lack mandatory release note fragments, use non-compliant branch naming, or skip required local validation tiers before submission.

Do I need to add release notes when contributing bug fixes to opencode-swarm?▼

Yes, contributing bug fixes to opencode-swarm requires adding mandatory unique release note fragments to ensure your changes are accepted without rework and pass project CI requirements.

What are the 5 tiers of local CI validation for git workflows?▼

The 5 tiers of local CI validation are mandatory pre-submission checks ensuring branch naming, commit formats, and release notes meet opencode-swarm standards to avoid CI failures on first submission.

Can I use standard git commit messages instead of conventional commits for opencode-swarm?▼

No, opencode-swarm enforces conventional commit formats and specific PR title standards to eliminate inconsistent, non-compliant contributions across all code changes and documentation updates.

Related Skills

Explore More Software Engineering Skills→
yxhpyyxhpy
42

qcc-git

Manage Git workflow for the qcc_plus project with branch and commit standards.

Community
Intermediate
TencentCloudBaseTencentCloudBase
1.1k

pr-review-fix

Analyze and resolve CI failures, review feedback, and merge conflicts across open GitHub pull requests.

Official
Advanced
TobiasGoetzTobiasGoetz

commit

Generate conventional commit messages and PR titles for Release Please.

Community
Intermediate
ehtbantonehtbanton

contributing-guide-generator

Generate a CONTRIBUTING.md file with open-source contribution guidelines.

Community
Basic