// 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.
| 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. |
git checkout main && git pull origin main
git checkout -b <type>/<short-description>
bun install --frozen-lockfile
Branch naming: <type>/<short-description> (e.g. feat/add-retry-backoff, fix/plan-sync-race).
Every commit MUST follow: <type>(<optional scope>): <description>
Rules:
| 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 moduleInvalid (rejected by CI):
WIP, fix stuff, Update README, feat: Add feature. (trailing period), Feat: (uppercase)cat .release-please-manifest.jsondocs/releases/v{NEXT_VERSION}.mdInclude:
Even one-line changes need release notes explaining why it matters.
# 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 120000
If a pre-existing unrelated failure exists, note it in the PR description but do NOT skip other tiers.
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 pass
release-please manages these automatically:
package.json version fieldCHANGELOG.md.release-please-manifest.jsonNever replace the release PR body, create tags/releases manually, or edit these files.
| Check | Validates |
|---|---|
quality | TypeScript compiles, Biome lint + format clean |
unit (Ubuntu, macOS, Windows) | Unit tests pass cross-platform |
integration (Ubuntu) | Integration tests pass |
security (Ubuntu) | Security & adversarial tests pass |
smoke (Ubuntu, macOS, Windows) | Package builds & smoke tests pass |
pr-standards | PR title is valid conventional commit |
check-duplicates | PR title not duplicate of open PR |
All uses: in .github/workflows/ must be pinned to full 40-char SHA with version comment:
- uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4
Find SHA: gh api repos/{owner}/{repo}/git/ref/tags/{tag} --jq '.object.sha'
main<type>(<scope>): <description>package.json version, CHANGELOG.md, or .release-please-manifest.jsondocs/releases/v{NEXT_VERSION}.md exists with release notestests/ subdirectoryuses: are SHA-pinnedEnable a high-quality swarm-like Claude Code workflow for the current session, and optionally execute a task immediately using that mode. Uses parallel subagents for breadth, independent reviewer validation for precision, and critic challenge for final confidence. Use when the user wants swarm-like behavior, higher review rigor, or maximum quality without sacrificing Claude Code speed.
Deep technical debt and CI stability audit for identifying test theater, missing or mis-scoped tests, actual and potential test failures, flaky-test risk, dependency/toolchain brittleness, and structural debt that prevents PRs from going green safely.
Apply when writing tests, modifying test files, fixing test failures, debugging CI failures, adding test coverage, creating adversarial tests, or reviewing any file under tests/. Also apply when implementing features or fixes that require corresponding test changes. Enforces bun:test framework rules, mock isolation, cross-platform compatibility (Linux, macOS, Windows), and CI pipeline awareness. Load this skill before touching any test file.
Apply when committing, pushing, opening a PR, writing a pull request, creating release notes, or updating a changelog. Enforces conventional commit format, mandatory release notes, 5-tier test suite, SHA-pinning for workflow changes, and correct PR body format.
Apply when implementing features, fixing bugs, debugging errors, investigating failures, tracing root causes, reviewing tech debt, tracing issues, planning fixes, or completing any task. Enforces parallel sub-agent implementation, independent adversarial review, and a 95% confidence gate before stopping.
Apply when planning fixes, investigating tech debt, architecting solutions, or diagnosing unknown issues. Search online for current documentation and state-of-the-art approaches before tracing through code.