swarm-implement · zaxbyhub — Claude Code skill: what it does, how to install
Adapts the canonical opencode-swarm implementation workflow for multi-file features, refactoring, and structured validation.
MIT ★ 539 updated 2026-10-29
npx skills add ZaxbyHub/opencode-swarm --skill swarm-implement -a claude-codeWhat swarm-implement does
The skill manages complex coding tasks that demand research, scoped plans, manual patching, and verification. It establishes a formal routine across multi-step changes so risky patches stay tested and documented.
It relies on update_plan during large tasks and uses runtime parallelism for repo reads. When necessary, it brings in targeted assistants like $engineering-conventions, $writing-tests, $running-tests, $qa-sweep, or $issue-tracer.
Reviewer verdicts go into persistent task artifacts instead of staying in volatile chat logs. In Codex environments, executing OpenCode /swarm commands is disallowed unless the user explicitly requests it.
What it helps with
- Structure multi-file refactoring and feature implementation
- Log review and critic verdicts into
08b-implementation-review.mdand09-final-critic.md - Run shell checks systematically after every code change
- Delegate tasks to helper skills for tests and QA sweeps
Example prompts for the agent
- Refactor the authentication service across multiple packages using swarm-implement
- Plan and execute a database migration fix following swarm-implement guidelines
- Address the memory leak in the worker pool and log all reviewer verdicts
How to install swarm-implement
1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill swarm-implement -a claude-code2Manually: put the files in place
~/.claude/skills/swarm-implement/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/swarm-implement/
1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill swarm-implement -a codex2Manually: put the files in place
.agents/skills/swarm-implement/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill swarm-implement -a cursor2Manually: put the files in place
.cursor/skills/swarm-implement/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ZaxbyHub/opencode-swarm .agents/skills/swarm-implement2Manually: put the files in place
.github/skills/swarm-implement/SKILL.md1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill swarm-implement -a gemini-cli2Platform CLI
gemini skills install https://github.com/ZaxbyHub/opencode-swarm --path .agents/skills/swarm-implementManually: put the files in place
.devin/skills/swarm-implement/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill swarm-implement -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about swarm-implement
How to install swarm-implement in Claude Code?
Run npx skills add ZaxbyHub/opencode-swarm --skill swarm-implement -a claude-code in your terminal.
What does swarm-implement do?
It orchestrates complex code changes through scoped planning, patch application, shell validation, and structured artifact reviews.
Can it run OpenCode swarm commands in Codex?
No, invoking OpenCode /swarm commands inside Codex is restricted unless the user directly asks to run OpenCode Swarm itself.
Source text
SKILL.md · MIT
--- name: swarm-implement description: Codex adapter for complex implementation work using the canonical opencode-swarm implementation workflow. Use for multi-file features, bug fixes, refactors, risky code changes, or tasks that benefit from exploration, scoped planning, implementation, review, and validation. metadata: audience: swarm-plugin --- # Swarm Implement Read and follow `../../../.opencode/skills/swarm-implement/SKILL.md` as the canonical workflow. Codex-specific execution notes: - Use `update_plan` for substantial multi-step work. - Use the runtime's parallel-execution capability for independent repo reads and searches. - Use `apply_patch` for manual edits. - Use focused shell validation after each meaningful change. - Bring in narrower skills as needed: `$engineering-conventions`, `$writing-tests`, `$running-tests`, `$qa-sweep`, or `$issue-tracer`. - Record reviewer and critic verdicts in durable task artifacts. For issue-tracer work, use `08b-implementation-review.md` and `09-final-critic.md`; otherwise use a task-local review artifact that names verdicts, evidence reviewed, and responses to every blocker. - Do not invoke OpenCode `/swarm` commands from Codex unless the user explicitly asks to operate OpenCode Swarm itself.
© ZaxbyHub · MIT · ZaxbyHub/opencode-swarm
Similar skills
All skills for Agent setup: memory, context, orchestration →swarm-implement by other authors comes first.