pr-review-fix · zaxbyhub, generated — Claude Code skill: what it does, how to install
This compatibility skill routes older pr-review-fix calls to the swarm-pr-feedback workflow for handling pull request feedback.
MIT ★ 539 updated 2026-10-29
npx skills add ZaxbyHub/opencode-swarm --skill pr-review-fix -a claude-codeWhat pr-review-fix does
pr-review-fix is a shim. When called, it loads ../../swarm-pr-feedback/SKILL.md and follows that skill’s workflow; it should not develop a separate process. For new work, the description directs users to swarm-pr-feedback instead.
The canonical workflow builds a complete feedback ledger and checks each review item before making edits. It also takes CI failures, conflicts, branch drift, and review surfaces into account. The user resolves GitHub review threads unless they explicitly delegate that task. Follow the repository’s commit and PR workflow before pushing or updating the PR.
What it helps with
- route older
pr-review-fixcalls to the canonical feedback workflow - gather review comments into a complete feedback ledger
- check each review item before editing
- account for CI failures, conflicts, and branch drift
- leave GitHub thread resolution to the user unless delegated
Example prompts for the agent
- Use
pr-review-fixto review this PR feedback and make a complete list before editing. - Check each review item before changing code, including CI failures and conflicts.
- Prepare fixes for the review, but leave GitHub threads unresolved unless I ask you to resolve them.
How to install pr-review-fix
1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill pr-review-fix -a claude-code2Manually: put the files in place
~/.claude/skills/pr-review-fix/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/pr-review-fix/
1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill pr-review-fix -a codex2Manually: put the files in place
.agents/skills/pr-review-fix/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill pr-review-fix -a cursor2Manually: put the files in place
.cursor/skills/pr-review-fix/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ZaxbyHub/opencode-swarm .opencode/skills/generated/pr-review-fix2Manually: put the files in place
.github/skills/pr-review-fix/SKILL.md1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill pr-review-fix -a gemini-cli2Platform CLI
gemini skills install https://github.com/ZaxbyHub/opencode-swarm --path .opencode/skills/generated/pr-review-fixManually: put the files in place
.devin/skills/pr-review-fix/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill pr-review-fix -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 pr-review-fix
How do I install pr-review-fix in Claude Code?
Run npx skills add ZaxbyHub/opencode-swarm --skill pr-review-fix -a claude-code. The skill file is at ~/.claude/skills/pr-review-fix/SKILL.md.
What does the pr-review-fix skill do?
It routes the call to swarm-pr-feedback, which collects and checks PR feedback before code changes.
Who resolves GitHub review threads?
The user does, unless they explicitly delegate resolution to the agent. Follow the repository’s commit and PR workflow before pushing or updating the PR.
Source text
SKILL.md · MIT
--- name: pr-review-fix description: > Legacy compatibility entry point for PR review feedback fixes. Use swarm-pr-feedback instead for new work; this shim exists so older references still route to the canonical feedback-closure workflow. metadata: effort: medium skill_origin: shim --- # PR Review Fix Compatibility Shim Use `../../swarm-pr-feedback/SKILL.md` as the canonical workflow. This legacy entry point must not grow an independent process. When invoked: 1. Load `../../swarm-pr-feedback/SKILL.md`. 2. Build the complete feedback ledger described there. 3. Verify each review item skeptically before editing. 4. Leave GitHub review-thread resolution to the user unless explicitly instructed. 5. Use the repository commit/PR workflow before pushing or updating the PR. Do not follow older `pr-review-fix` behavior that batches comments without first ingesting CI failures, conflicts, branch drift, and all review surfaces.
© ZaxbyHub · MIT · ZaxbyHub/opencode-swarm
Similar skills
All skills for Code review and refactoring →pr-review-fix by other authors comes first.