Diagnose Playwright Failure as Product Bug
appsmithorg/appsmith
Investigates a stubbornly failing Playwright test as a possible product bug, using error output, screenshots, traces and server code, and writes a structured bug report.
A skill your agent uses 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…
Install Issue Tracer
$ npx skills add ZaxbyHub/opencode-swarm --skill issue-tracer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ZaxbyHub/opencode-swarm issue-tracer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ZaxbyHub/opencode-swarm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/issue-tracer .claude/skills/issue-tracer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "issue-tracer" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.agents/skills/issue-tracer into .claude/skills/issue-tracer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-tracer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ZaxbyHub/opencode-swarm/tree/main/.agents/skills/issue-tracerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ZaxbyHub/opencode-swarm --skill issue-tracer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ZaxbyHub/opencode-swarm issue-tracer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ZaxbyHub/opencode-swarm.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/issue-tracer .agents/skills/issue-tracer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "issue-tracer" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.agents/skills/issue-tracer into .agents/skills/issue-tracer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-tracer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ZaxbyHub/opencode-swarm --skill issue-tracer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ZaxbyHub/opencode-swarm issue-tracer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ZaxbyHub/opencode-swarm.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/issue-tracer .cursor/skills/issue-tracer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "issue-tracer" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.agents/skills/issue-tracer into .cursor/skills/issue-tracer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-tracer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ZaxbyHub/opencode-swarm.git --path .agents/skills/issue-tracer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ZaxbyHub/opencode-swarm --skill issue-tracer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ZaxbyHub/opencode-swarm issue-tracer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ZaxbyHub/opencode-swarm.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/issue-tracer .gemini/skills/issue-tracer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "issue-tracer" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.agents/skills/issue-tracer into .gemini/skills/issue-tracer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-tracer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ZaxbyHub/opencode-swarm issue-tracerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ZaxbyHub/opencode-swarm --skill issue-tracer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ZaxbyHub/opencode-swarm.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/issue-tracer .github/skills/issue-tracer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "issue-tracer" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.agents/skills/issue-tracer into .github/skills/issue-tracer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-tracer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ZaxbyHub/opencode-swarm --skill issue-tracer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ZaxbyHub/opencode-swarm issue-tracer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ZaxbyHub/opencode-swarm.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/issue-tracer .opencode/skills/issue-tracer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "issue-tracer" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.agents/skills/issue-tracer into .opencode/skills/issue-tracer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-tracer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
issue-tracer- GitHub stars
- 494
- Token cost
- ~383 tokens
- SKILL.md length
- 98 words
- Files
- 2
- Skills in repo
- 91
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses 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…
- Prepare a PR for an issue
- SKILL.md covers Codex Tools, Gates and Delegation and Scripts and Publication
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Confusing runtime behavior
What it does
Issue Tracer is an agent skill from ZaxbyHub/opencode-swarm. 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.
Its SKILL.md is about 380 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Testing & QA, covering Internationalization, QA and bug reports and Failing and flaky tests. The repository describes itself as: Architect-centric agentic swarm plugin for OpenCode. Hub-and-spoke orchestration with SME consultation, code generation, and QA review. The licence is MIT.
When your agent uses it
- Prepare a PR for an issue
- Confusing runtime behavior
Example prompts
- “/issue-tracer”
What it can do on your machine
Read from SKILL.md and the folder at commit b63a4bd. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Issue Tracer loads about 383 tokens when it runs. Until then it costs about 120 tokens; SKILL.md has 98 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from ZaxbyHub/opencode-swarm at commit b63a4bd, republished under its MIT licence (© ZaxbyHub). 98 words, ~383 tokens.
Download SKILL.mdSave it as
.claude/skills/issue-tracer/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- 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.
- audience
- swarm-plugin
- metadata.version
- 3.0.0
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. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .agents/skills/issue-tracer of ZaxbyHub/opencode-swarm.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit b63a4bd
Compare with similar skills
Issue Tracer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Issue Tracer this skillZaxbyHub/opencode-swarm | 494 | — | ~383 | Automated safety check: Pass | MIT | |
| Diagnose Playwright Failure as Product Bugappsmithorg/appsmith | 41k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| AI Bug Triagepetrkindlmann/qa-skills | 170 | — | ~5.2k | Automated safety check: Pass | MIT | |
| Bug To Patch GeneratorArabelaTso/Skills-4-SE | 253 | — | ~4.4k | Automated safety check: Pass | Apache-2.0 | |
| Dynamo Jira TicketDynamoDS/Dynamo | 2k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Trx Analysismicrosoft/vstest | 969 | — | ~1.8k | Automated safety check: Pass | MIT |
Similar skills
AI Bug Triage
petrkindlmann/qa-skills
Hybrid fingerprint + LLM pipeline for bug classification, deduplication, and ticket generation.
Bug To Patch Generator
ArabelaTso/Skills-4-SE
Generate code fixes and patches from bug reports, failing test cases, error messages, and stack traces.
Dynamo Jira Ticket
DynamoDS/Dynamo
Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.
- Official
Trx Analysis
microsoft/vstest
Parse and analyze Visual Studio TRX test result files. An agent skill from microsoft/vstest.
- Official
Triage
withastro/triagebot-action
Triage a bug report against the triagebot-action codebase. An agent skill from withastro/triagebot-action.
More from ZaxbyHub/opencode-swarm
All 91 skills in this repoCodebase Review Swarm
ZaxbyHub/opencode-swarm
Runs an evidence-gated, quote-grounded audit of a codebase for security, QA, accessibility, performance and more, and writes a verified report without changing source files.
Issue Tracer
ZaxbyHub/opencode-swarm
Drives a bug report from validation and root-cause tracing through a critic-reviewed plan, an approved minimal fix and a PR-ready closure, never merging without recorded human approval.
Commit and PR Publishing for Codex
ZaxbyHub/opencode-swarm
Codex adapter for opencode-swarm that governs commits, pushes, draft PRs, PR body updates and CI closeout, deferring to the repo's canonical commit-pr protocol.
Durable Session State
ZaxbyHub/opencode-swarm
Keeps plans, decisions, evidence and reviewer verdicts in small files so long multi-phase tasks survive context compaction and session resumes.
Swarm PR Feedback Closer
ZaxbyHub/opencode-swarm
Ingests existing pull request feedback such as review comments and CI failures, verifies each claim, fixes confirmed issues and reports closure status for every item.
Swarm PR Subscribe
ZaxbyHub/opencode-swarm
Monitor a pull request after creation and act autonomously on pushed PR activity.
Related
Categories
Questions about Issue Tracer
What does Issue Tracer do?
A skill your agent uses 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…. Issue Tracer is an agent skill from ZaxbyHub/opencode-swarm. 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.
When should I use Issue Tracer?
Issue Tracer fits situations like: prepare a PR for an issue; confusing runtime behavior.
How do I install Issue Tracer in Claude Code?
Run `npx skills add ZaxbyHub/opencode-swarm --skill issue-tracer -a claude-code`. Or copy the skill folder (.agents/skills/issue-tracer in ZaxbyHub/opencode-swarm) into .claude/skills/issue-tracer in your project. Claude Code loads it when a task matches its description.
How do I install Issue Tracer in Codex?
Run `npx skills add ZaxbyHub/opencode-swarm --skill issue-tracer -a codex`. Or copy the skill folder (.agents/skills/issue-tracer in ZaxbyHub/opencode-swarm) into .agents/skills/issue-tracer in your project. Codex loads it when a task matches its description.
Can I use Issue Tracer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ZaxbyHub/opencode-swarm --skill issue-tracer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/issue-tracer, .gemini/skills/issue-tracer, .github/skills/issue-tracer and .opencode/skills/issue-tracer in your project.
What does Issue Tracer need to run?
SKILL.md names no scripts, command-line tools or credentials: Issue Tracer is instructions for the agent only.
Does Issue Tracer access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Issue Tracer safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Issue Tracer use?
Issue Tracer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Issue Tracer use?
About 383 tokens (SKILL.md is roughly 1.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Issue Tracer?
Skills that share tags, products or a category with Issue Tracer: Diagnose Playwright Failure as Product Bug (appsmithorg/appsmith, 41k stars), AI Bug Triage (petrkindlmann/qa-skills, 170 stars), Bug To Patch Generator (ArabelaTso/Skills-4-SE, 253 stars) and Dynamo Jira Ticket (DynamoDS/Dynamo, 2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Issue Tracer?
ZaxbyHub (a GitHub organization) maintains it in ZaxbyHub/opencode-swarm, which has 494 GitHub stars. The repository holds 91 skills in this directory. The repository was last updated on October 10, 2026.
Source: ZaxbyHub/opencode-swarm on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.