issue-tracer · zaxbyhub, claude — Claude Code skill: what it does, how to install
issue-tracer takes a bug from reproduction to a PR-ready fix: locates the cause, plans the change, and puts it through critic review.
MIT ★ 539 updated 2026-10-29
npx skills add ZaxbyHub/opencode-swarm --skill issue-tracer -a claude-codeWhat issue-tracer does
Hand it a bug report, a regression or a red test and it carries the work through to closure. The real protocol sits in .opencode/skills/issue-tracer/SKILL.md: reproduce the fault, reason your way to the cause, build a fix plan with no gaps, then wipe out the whole class of recurrence. The run ends with a PR that is ready to open.
Three checkpoints go to a subagent. Plan critic (phase 3), implementation review (4.5) and final critic (4.6) run through Agent and see only the diff plus artifacts described in .opencode/skills/issue-tracer/references/critic-gate.md. No Agent or Task tool? The skill logs the delegation failure, runs a fallback labelled as such, and says so in the report. trace-init.sh <issue-slug> sets up the trace directory, scan-deferred.sh blocks leftover work. Commits and PRs go through .claude/skills/commit-pr/SKILL.md, only when you ask.
On Claude this file is a thin adapter. The canonical protocol has to exist at that .opencode path inside the repo, because there is nothing else for the adapter to follow. Run the init script from the repo root.
What it helps with
- reproduce a reported bug and capture the steps
- find the root cause of a regression instead of the symptom
- plan a fix that leaves no gaps
- kill the class of bug that keeps coming back
- get a fix ready for a pull request
Example prompts for the agent
- Trace issue #412: reproduce it, find the cause, and get a PR ready.
test_checkout.pykeeps failing — follow the regression back and propose a fix.- Take the timeout bug report through critic review and close it out with a PR.
How to install issue-tracer
1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill issue-tracer -a claude-code2Manually: put the files in place
~/.claude/skills/issue-tracer/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/issue-tracer/
1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill issue-tracer -a codex2Manually: put the files in place
.agents/skills/issue-tracer/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill issue-tracer -a cursor2Manually: put the files in place
.cursor/skills/issue-tracer/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ZaxbyHub/opencode-swarm .claude/skills/issue-tracer2Manually: put the files in place
.github/skills/issue-tracer/SKILL.md1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill issue-tracer -a gemini-cli2Platform CLI
gemini skills install https://github.com/ZaxbyHub/opencode-swarm --path .claude/skills/issue-tracerManually: put the files in place
.devin/skills/issue-tracer/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill issue-tracer -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 issue-tracer
How do I install issue-tracer in Claude Code?
Run npx skills add ZaxbyHub/opencode-swarm --skill issue-tracer -a claude-code; the skill lands at ~/.claude/skills/issue-tracer/SKILL.md.
What does issue-tracer do?
It walks a bug or a failing test through reproduction, cause localization and fix planning, then assembles a pull request. Critic subagents handle the checkpoints along the way.
What if the Agent tool is unavailable?
The skill records the delegation failure, switches to a fallback path that is clearly labelled, and discloses it in the report.
Source text
SKILL.md · MIT
--- name: issue-tracer description: > Use when asked to trace, investigate, root-cause, reproduce, plan, fix, resolve, close, or prepare a PR for an issue, bug report, defect, regression, failing test, or confusing runtime behavior. This Claude Code adapter delegates to the canonical protocol at .opencode, which owns the Full-Resolution Contract, reproduction, reasoning-guided localization, no-gap fix planning, recurrence-class eradication, independent critic and implementation review, and PR-ready closure. metadata: version: 3.0.0 audience: swarm-plugin --- # Issue Tracer Follow the canonical workflow at `../../../.opencode/skills/issue-tracer/SKILL.md`. ## Claude Code Tools - File-edit: `Edit`, `Write`, `MultiEdit`. Tasklist: `TodoWrite`. Web: `WebFetch`, `WebSearch`. - Search: `Grep`, `Glob`, `Read`. Subagent: `Agent` (legacy alias `Task`). Bash: for scripts/git. ## Gates and Delegation Plan critic (Phase 3), implementation review (Phase 4.5), and final critic (Phase 4.6) run via `Agent` subagent tool. Receive only diff and artifacts from the canonical protocol's `.opencode/skills/issue-tracer/references/critic-gate.md`. If `Agent`/`Task` is unavailable, record the delegation failure, run the labeled fallback, and disclose it. ## Scripts and Publication Trace directory created by `.opencode/skills/issue-tracer/scripts/trace-init.sh <issue-slug>` (from repo root). Deferred-work gate: `.opencode/skills/issue-tracer/scripts/scan-deferred.sh`. Publication via `.claude/skills/commit-pr/SKILL.md` only when user asks to commit/push/open PR.
© ZaxbyHub · MIT · ZaxbyHub/opencode-swarm
Similar skills
All skills for Agent setup: memory, context, orchestration →issue-tracer by other authors comes first.