canon-feedback-triagelisted

# Canon feedback triage Consume the feedback queue that `canon feedback --github` fills. Turn an open `feedback` issue into a scoped fix or a plan, then link the issue so merge closes it. Run from the toolkit repo root. This skill reads GitHub issues, not local `.canon/review/` files. Those are ephemeral session scratch. The durable, cross-project queue is GitHub. ## Guards - If `gh` is not on PATH, stop: `�� gh CLI not found. Install it to read feedback issues.` - If `gh auth status` fails, stop: `❌ gh is not authenticated. Run gh auth login.` - If no open `feedback` issues exist, stop: `✅ No open feedback issues.` ## Step 1: list the queue Fetch open feedback issues: ```bash gh issue list --label feedback --state open --json number,title,url --jq '.[] | "#\(.number)\t\(.title)\t\(.url)"' ``` Print each as a numbered line with its issue number, title, and URL. Do not open bodies yet. Ask which to triage, and accept "all" to work them in order. ## Step 2: read and classify For each picked issue, read the body: ```bash gh issue view <n> --json title,body,labels --jq '"\(.title)\n\n\(.body)"' ``` Classify against the toolkit's own surfaces. Score in this order and stop at the first match: 1. **Direct fix.** One surface, one file, no architectural choice. A typo, a stale reference, a one-line rule or doc correction, a single wording fix. Route straight to the edit. 2. **Plan-worthy.** Multiple files, a new skill or rule, a behavior change, or a cross-surface move. R