issue-tracer · zaxbyhub — Claude Code skill: what it does, how to install
issue-tracer walks a bug from reproduction to a PR-ready fix: locate the cause, plan the patch, get it reviewed.
MIT ★ 539 updated 2026-10-29
npx skills add ZaxbyHub/opencode-swarm --skill issue-tracer -a claude-codeWhat issue-tracer does
Reach for it when you hand over a bug report, a regression, a failing test or runtime behaviour you can't explain. The skill file is a thin adapter for Codex: the real procedure sits in .opencode/skills/issue-tracer/SKILL.md, and this one points there and maps the tooling.
Edits go through apply_patch, the task list through update_plan, web lookups through web with cited URLs. Shell work uses rg, git, gh, plus your tests and builds. Three gates (a plan critic in phase 3, implementation review in 4.5, a final critic in 4.6) expect a subagent. When none is available the skill logs the failure, runs a labelled fallback and discloses it in the report; gate artefacts come from .opencode/skills/issue-tracer/references/critic-gate.md.
trace-init.sh <issue-slug> creates the trace directory from the repo root, scan-deferred.sh is the deferred-work gate. Commits, pushes and PRs happen only when you ask, via .agents/skills/commit-pr/SKILL.md.
What it helps with
- reproduce a failing test and pin down its cause
- trace a regression back through a bug report
- draft a fix plan with no gaps left open
- wipe out a whole class of repeat failures
- carry an issue to a PR with the diff reviewed
Example prompts for the agent
- Trace this bug report: reproduce the crash, find the cause, then draft a fix plan.
- Run
trace-init.sh <issue-slug>and drop the repro steps and test output in there. - Run
scan-deferred.shand list what got left for later.
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 .agents/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 .agents/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 takes an issue through reproduction, cause localization and fix planning, then sends the result to a critic. What comes out is a closure ready for a PR.
Do the review gates need a subagent?
The plan critic, the implementation review and the final critic all require delegation. With no subagent around, the skill records the failure and runs a labelled fallback it discloses.
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 Codex 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`. ## Codex Tools - File-edit: `apply_patch`. Tasklist: `update_plan`. Web: `web` (cite URLs). - Shell: `rg`, `git`, `gh`, tests, builds. Subagent dispatch: per your runner config. ## Gates and Delegation Plan critic (Phase 3), implementation review (Phase 4.5), and final critic (Phase 4.6) require subagent delegation when available. Receive only diff and artifacts from the canonical protocol's `.opencode/skills/issue-tracer/references/critic-gate.md`. When unavailable, record the 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 `.agents/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.