Skip to main content
skill CX Codex

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

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add ZaxbyHub/opencode-swarm --skill issue-tracer -a claude-code
Open on GitHub

What 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.py keeps 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-code

2Manually: put the files in place

~/.claude/skills/issue-tracer/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/issue-tracer/

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.

issue-tracer ZaxbyHub issue-tracer walks a bug from reproduction to a PR-ready fix: locate the cause, plan the patch, get it reviewed. CX Codex +1 ★ 539repo stars issue-tracer ZaxbyHub issue-tracer drives bug reports from reproduction and root-cause analysis to verified PRs under a strict full-resolution contract. CX Codex +1 ★ 539repo stars om-fix-issue open-mercato om-fix-issue — a skill for Claude Code and Codex that diagnoses a tracker issue, verifies a regression test, and leaves staged changes for manual review without committing or opening a PR. CX Codex +1 502installs om-auto-fix-issue open-mercato The om-auto-fix-issue Claude Code skill takes a tracker issue through a bug-fix or feature workflow. Give it an issue reference or a plain description of the problem. CX Codex +1 4,700installs debug-issue tirth8205 The debug-issue Claude Code skill traces bugs through a code graph. It kicks in to locate a fault, follow its execution path, and assess the reach of a fix. CX Codex +1 1,100installs fix-issue frappe fix-issue turns a bug report into a fix: a subagent extracts the facts, the main agent reproduces the bug and traces the cause without inheriting the reporter's guesses. CX Codex +1 431installs pr-issue-resolve safayavatsal The pr-issue-resolve plugin examines pull requests and implements the changes reviewers request. Use it to quickly work through code review feedback and apply corrections. ★ 1,013repo stars ns-execution-gitlab-issue nextstage-brasil ns-execution-gitlab-issue executes GitLab issues end-to-end with worktree isolation, automated status changes, atomic delivery, and merge requests. CX Codex +1 165installs

From the same set121

The whole set →
restore-internals-seams-in-finally-blocks-after-each-test restore-internals-seams-in-finally-blocks-after-each-test is a Claude Code skill that directs agents to restore original _internals in finally after each test of error paths through DI seams. CX Codex +1 ★ 539repo stars check-skill-provenance-stamps-before-archiving-knowledge-entries check-skill-provenance-stamps-before-archiving-knowledge-entries is a Claude Code skill that checks source_refs and UUIDs before archiving knowledge entries, stopping removal if an active skill depends on one. CX Codex +1 ★ 539repo stars consult consult enforces an advisory protocol with strict read-before-cite checks and explicit uncertainty levels. CX Codex +1 ★ 539repo stars run-affected-test-suite-end-to-end-after-multi-file-signature-ch run-affected-test-suite-end-to-end-after-multi-file-signature-ch is a Claude Code skill that runs affected tests and checks every call site after function signatures change across files. CX Codex +1 ★ 539repo stars confirm-failures-are-causally-linked-to-the-task-before-reportin confirm-failures-are-causally-linked-to-the-task-before-reportin is a Claude Code skill that separates pre-existing test failures from new regressions before rejecting work. CX Codex +1 ★ 539repo stars writing-tests writing-tests sets test-authoring rules for the opencode-swarm repository. Use it before changing tests that involve mocks, temporary paths, or regression checks. CX Codex +1 ★ 539repo stars run-affected-test-file-in-isolation-and-in-co-run-with-its-test- run-affected-test-file-in-isolation-and-in-co-run-with-its-test- is a Claude Code skill that makes the agent run tests in isolation and with sibling files after mock cleanup changes. CX Codex +1 ★ 539repo stars update-or-delete-tests-that-assert-intentionally-removed-behavio update-or-delete-tests-that-assert-intentionally-removed-behavio is a Claude Code skill for revising or removing tests of deliberately removed behavior. It applies to code changes that retire a code path. CX Codex +1 ★ 539repo stars

Project sponsors

Companies that keep this analytics open