Bug Tracker

Work the public bug tracker — the separate GitHub repo where users and testers file bug reports, feedback, and feature requests against a shipped product — through its actionable queue one issue at a time: investigate & verify, tag, mark in-progress, solve via subagent (similar to work-on-issues), comment on the tracker with resolution details, mark resolved, and close.

This handles public reports filed against a separate tracker repo with the source code located in the current working directory. The label taxonomy it drives is the one /init-bug-tracker creates.

Every comment posted to the tracker during a run starts with:

> *This was generated by AI during bug-tracker triage.*

Resolve the tracker repo

In order:

1. An explicit argument: /bug-tracker <owner/repo>. A bare issue number (/bug-tracker 42) resolves against the tracker below and jumps straight to step 2.
2. A tracker already recorded for this repo — the ### Bug tracker sub-block under ## Agent skills in CLAUDE.md or AGENTS.md.
3. Ask the maintainer which repo holds the reports, then record it there so the next run doesn't ask again.