QA Sweep
ZaxbyHub/opencode-swarm
Apply when implementing features, fixing bugs, debugging errors, investigating failures, tracing root causes, reviewing tech debt, tracing issues, planning fixes, or completing any task.
Log a concrete issue (bug, technical debt, open design problem, or retire candidate) into tracker/ with elaboration — symptoms/impact, affected code links, root-cause notes, fix approaches, and…
Install Track Issue
$ npx skills add cdiggins/plato --skill track-issue -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cdiggins/plato track-issue --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/cdiggins/plato.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/track-issue .claude/skills/track-issue && 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 "track-issue" agent skill from https://github.com/cdiggins/plato/tree/main/.claude/skills/track-issue into .claude/skills/track-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "track-issue", 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/cdiggins/plato/tree/main/.claude/skills/track-issueType 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 cdiggins/plato --skill track-issue -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cdiggins/plato track-issue --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cdiggins/plato.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/track-issue .agents/skills/track-issue && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "track-issue" agent skill from https://github.com/cdiggins/plato/tree/main/.claude/skills/track-issue into .agents/skills/track-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "track-issue", 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 cdiggins/plato --skill track-issue -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cdiggins/plato track-issue --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cdiggins/plato.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/track-issue .cursor/skills/track-issue && 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 "track-issue" agent skill from https://github.com/cdiggins/plato/tree/main/.claude/skills/track-issue into .cursor/skills/track-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "track-issue", 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/cdiggins/plato.git --path .claude/skills/track-issue--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 cdiggins/plato --skill track-issue -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cdiggins/plato track-issue --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cdiggins/plato.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/track-issue .gemini/skills/track-issue && 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 "track-issue" agent skill from https://github.com/cdiggins/plato/tree/main/.claude/skills/track-issue into .gemini/skills/track-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "track-issue", 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 cdiggins/plato track-issueInstalls 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 cdiggins/plato --skill track-issue -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cdiggins/plato.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/track-issue .github/skills/track-issue && 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 "track-issue" agent skill from https://github.com/cdiggins/plato/tree/main/.claude/skills/track-issue into .github/skills/track-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "track-issue", 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 cdiggins/plato --skill track-issue -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cdiggins/plato track-issue --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cdiggins/plato.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/track-issue .opencode/skills/track-issue && 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 "track-issue" agent skill from https://github.com/cdiggins/plato/tree/main/.claude/skills/track-issue into .opencode/skills/track-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "track-issue", 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
track-issue- GitHub stars
- 106
- Token cost
- ~1.7k tokens
- SKILL.md length
- 473 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
Log a concrete issue (bug, technical debt, open design problem, or retire candidate) into tracker/ with elaboration — symptoms/impact, affected code links, root-cause notes, fix approaches, and…
- Works in 5 steps: Understand the issue → Locate the evidence (before writing… → Create the issue (script) → …
- The user says /track-issue
- SKILL.md covers Steps and Rules
- Calls python
What it does
Track Issue is an agent skill from cdiggins/plato. Log a concrete issue (bug, technical debt, open design problem, or retire candidate) into tracker/ with elaboration — symptoms/impact, affected code links, root-cause notes, fix approaches, and simplest fix. Use when the user says /track-issue, "file an issue", "log this bug", "track this debt", "this should be retired", or an agent discovers out-of-scope debt/bugs mid-task.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Technical debt and Root cause analysis. The repository describes itself as: A simple and efficient cross-platform programming language. The licence is MIT.
When your agent uses it
- The user says /track-issue
- Track this debt
- This should be retired
- An agent discovers out-of-scope debt/bugs mid-task
Example prompts
- “file an issue”
- “log this bug”
- “track this debt”
- “/track-issue”
Requirements
- Python 3
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit f6e02cf. 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
Shell commands in SKILL.md call:
python
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
Track Issue loads about 1.7k tokens when it runs. Until then it costs about 97 tokens; SKILL.md has 473 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 cdiggins/plato at commit f6e02cf, republished under its MIT licence (© cdiggins). 473 words, ~1,656 tokens.
Download SKILL.mdSave it as
.claude/skills/track-issue/SKILL.md (or your agent's skills folder).- name
- track-issue
- description
- Log a concrete issue (bug, technical debt, open design problem, or retire candidate) into tracker/ with elaboration — symptoms/impact, affected code links, root-cause notes, fix approaches, and simplest fix. Use when the user says /track-issue, "file an issue", "log this bug", "track this debt", "this should be retired", or an agent discovers out-of-scope debt/bugs mid-task.
- argument-hint
- <the issue, in a phrase or paragraph>
<!-- GENERATED by the WorkQuarry installer — do not hand-edit. Edit the source in the workquarry submodule and re-run install.py. -->track-issue — capture and elaborate a concrete issue
Sibling of /track-idea, for defects and liabilities rather than opportunities:
type: bug | debt | problem | retire (use /track-idea for idea/feature).
Mechanical parts go through tools/track.py; investigation is yours.
Process reference: tracker/readme.md. Areas are configured in tracker/config.json.
Steps
1. Understand the issue
From the argument or recent conversation. Pick the type:
- bug — observed wrong behavior
- debt — code that works but resists change/reuse (coupling, duplication, missing tests, raw types, dead flags)
- problem — open design question that needs an answer before dependent work
- retire — code, doc, or feature that should be deleted or deprecated If ambiguous between two types, pick the one whose closing action is clearer (a bug closes with a fix; debt closes with a refactor; a problem closes with an ADR; retire closes with a deletion).
2. Locate the evidence (before writing anything)
Unlike ideas, issues must point at something real:
- Find the affected files/symbols with
Grep/Glob; recordpath:linewhere possible. - For bugs: capture the repro or the observed-vs-expected behavior from conversation, logs, or a quick check. Do not run long builds/tests just to file — note "unverified" instead.
- Check
tracker/issues/+BACKLOG.md/DONE.mdfor an existing issue covering the same thing — enrich it rather than duplicate. - Check
tracker/decisions/for ADRs that explain why the current state is intentional (if one does, say so in the body — the issue may be a supersede-proposal, not a defect).
3. Create the issue (script)
python tools/track.py new --title "<short imperative title>" --area <one of your configured areas> --type <bug|debt|problem|retire> --links "<comma-separated paths/ids>"Always reason about priority — don't default to ?. Weigh: impact severity × frequency, whether it blocks other backlog items, and cost growth if deferred (debt compounds; bugs usually don't). State the reasoning in the Priority section below. Effort/risk likewise when evident (risk for retire = blast radius). The script regenerates BACKLOG.md — never hand-edit it; later changes go through track.py set.
Show full SKILL.md (182 more words)Show less
4. Elaborate — append body to the issue file
Sections after the frontmatter; terse, evidence-first. Skip a section only when empty.
## Issue
What is wrong / at risk, one paragraph. For bugs: observed vs expected, repro steps or "unverified — reported in conversation <date>".
## Impact
Who/what hits this and how often. What it blocks or slows. Cost of doing nothing.
## Affected code
- path:line — role in the problem.
## Cause / analysis
Root-cause hypothesis (bugs), why the debt accumulated (debt), what makes the question hard (problem), why the code is obsolete (retire). Mark speculation as such.
## Priority
Why this priority: severity × frequency, what it blocks, cost of deferral.
## Dependencies
- Blocked by: [ids/paths] — what must land first.
- Blocks: [ids] — backlog items this gates.
- Touches: shared code/areas where concurrent work would collide.
## Fix approaches
1–3 options with one-line trade-offs. For problems: candidate answers; note that closing should produce an ADR + follow-up issues.
## Bedrock
The version of this fix that leaves the architecture stronger — patch the symptom vs. fix the invariant. Name the specific seam, invariant, boundary, or file it strengthens (the invariant the bug violated, the boundary that let it through), and what future changes it makes cheaper or safer. Then a one-line verdict: **simplest / right / simplest-along-the-grain**. When the verdict is simplest-along-the-grain, state exactly what the simple fix must NOT do so the stronger design stays reachable.
## Done means
2–5 verifiable statements of what "fixed" looks like, written as checkboxes. Optional at capture; required before promotion to `ready` for bug/debt/feature. Include the verification step as its own box when a fix needs runtime confirmation — a landed fix awaiting verification is not done.
- [ ] the repro no longer reproduces
- [ ] regression test added and passing
- [ ] verified in the running app
Whoever lands the fix ticks these in the commit that satisfies them; when all are ticked the item is closed in the following commit. Progress is read from these boxes — never stored as a percentage.
## Simplest fix
Smallest change that resolves it, with pros/cons: what you get, what you give up or risk.
## Prevention
How to keep this class of issue from recurring:
- Existing backlog items that would already prevent it — link and say how.
- Tests: the missing test that would have caught it (regression test = part of the fix; class-level test coverage = its own issue).
- New features/tooling ideas (invariants, typed APIs, checks, CI gates) — offer to file each via /track-idea or as a capture-only issue.The Bedrock section may be a single line — "No architectural leverage here — simplest wins." — when that is true. What is NOT allowed: generic design-principle recitation that names no concrete file, seam, or invariant.
Ground everything in what you actually found in step 2 — real paths, real symbols, no invented behavior.
5. Report to the user
Give: the new id (linked), one-line impact statement, recommended fix, chosen priority + why, and whether it is safe to defer. If Prevention surfaced new test/feature ideas, list them and ask which to file (capture-only). Do not paste the whole body back.
Rules
- One issue per file. A cluster of related debt: file the umbrella, list members in the body, split only when someone starts work.
- Never renumber or reuse ids. The script owns allocation.
- Filed mid-task while working on something else: keep it capture-quality (steps 1–3 + a short Issue/Affected-code body), don't derail the main task with full elaboration.
- The issue must stand alone without this conversation's transcript.
© cdiggins, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/track-issue of cdiggins/plato.
Open the folder on GitHubat commit f6e02cf
Compare with similar skills
Track Issue 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 |
|---|---|---|---|---|---|---|
| Track Issue this skillcdiggins/plato | 106 | — | ~1.7k | Automated safety check: Pass | MIT | |
| QA SweepZaxbyHub/opencode-swarm | 490 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Code Design Rationale Investigatorcursor/plugins | 10k | 9 repos | ~2.6k | Automated safety check: Pass | None | |
| Systematic Code Refactoringluongnv89/claude-howto | 42k | — | ~3k | Automated safety check: Pass | MIT | |
| OpenLogi macOS Permissions TriageAprilNEA/OpenLogi | 23k | — | ~2.5k | Automated safety check: Notes | Apache-2.0 | |
| Bug Finder for daisyUIsaadeghi/daisyui | 43k | — | ~2.3k | Automated safety check: Pass | MIT |
Similar skills
- Official
Code Design Rationale Investigator
cursor/plugins
Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.
Systematic Code Refactoring
luongnv89/claude-howto
Guides refactoring in phases based on Martin Fowler's method: research, test coverage check, planning and small tested steps, with your approval at each phase.
OpenLogi macOS Permissions Triage
AprilNEA/OpenLogi
Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.
Bug Finder for daisyUI
saadeghi/daisyui
Investigates suspected bugs in the daisyUI monorepo through read-only analysis, then writes a decision-ready fix plan in tmp/bugs without changing any product code.
Root Cause Debugging
garrytan/gstack
Investigates bugs, errors and stack traces in phases and requires a root-cause hypothesis to be confirmed before any fix is written.
More from cdiggins/plato
Track Backlog
cdiggins/plato
View and manage the tracker backlog — show in-progress work, current priorities, sprint contents; triage untriaged items; promote ideas to ready; plan a sprint (big rocks + little rocks…
Track Idea
cdiggins/plato
Log a new idea into tracker/ with elaboration — assumptions, design decisions, related work links, approach brainstorm, and simplest implementation.
Write Docs
cdiggins/plato
Read BEFORE writing or editing any durable document in this repo — docs/.md, stdlib/.md, tracker/readme.md, AGENTS.md, any README.
Write Readme
cdiggins/plato
Write or review a project README.md in plain technical-writer prose — problem it solves and doesn't, honest assessment of tested vs untested, trade-offs, prior art, organization, and usage.
Related
Categories
Questions about Track Issue
What does Track Issue do?
Log a concrete issue (bug, technical debt, open design problem, or retire candidate) into tracker/ with elaboration — symptoms/impact, affected code links, root-cause notes, fix approaches, and…. Track Issue is an agent skill from cdiggins/plato. Log a concrete issue (bug, technical debt, open design problem, or retire candidate) into tracker/ with elaboration — symptoms/impact, affected code links, root-cause notes, fix approaches, and simplest fix.
When should I use Track Issue?
Track Issue fits situations like: the user says /track-issue; track this debt; this should be retired; an agent discovers out-of-scope debt/bugs mid-task.
How do I install Track Issue in Claude Code?
Run `npx skills add cdiggins/plato --skill track-issue -a claude-code`. Or copy the skill folder (.claude/skills/track-issue in cdiggins/plato) into .claude/skills/track-issue in your project. Claude Code loads it when a task matches its description.
How do I install Track Issue in Codex?
Run `npx skills add cdiggins/plato --skill track-issue -a codex`. Or copy the skill folder (.claude/skills/track-issue in cdiggins/plato) into .agents/skills/track-issue in your project. Codex loads it when a task matches its description.
Can I use Track Issue 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 cdiggins/plato --skill track-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/track-issue, .gemini/skills/track-issue, .github/skills/track-issue and .opencode/skills/track-issue in your project.
What does Track Issue need to run?
Going by SKILL.md and its folder, Track Issue needs the command-line tools its instructions call (python). Our summary lists: Python 3.
Does Track Issue 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 Track Issue 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 Track Issue use?
Track Issue 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 Track Issue use?
About 1.7k tokens (SKILL.md is roughly 6.6k 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 Track Issue?
Skills that share tags, products or a category with Track Issue: QA Sweep (ZaxbyHub/opencode-swarm, 490 stars), Code Design Rationale Investigator (cursor/plugins, 10k stars), Systematic Code Refactoring (luongnv89/claude-howto, 42k stars) and OpenLogi macOS Permissions Triage (AprilNEA/OpenLogi, 23k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Track Issue?
cdiggins (a GitHub user) maintains it in cdiggins/plato, which has 106 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on September 26, 2026.
Source: cdiggins/plato on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.