github-issue-triagelisted

# GitHub Issue Triage Assess a GitHub issue by verifying its claims against actual code, checking fit against product vision, and leaving a structured comment with findings, corrections, and a test plan. **This skill assesses and comments — it does not implement fixes.** Fixes follow a separate deliberate step per this repo's Recommendation Assessment mandate in CLAUDE.md. ## The Prompt (canonical form) > Triage issue #N. Start by fetching the full issue details (title, body, comments, labels, linked PRs). Then verify every factual claim in the issue against the actual running code — grep the relevant source, read the actual files/lines, and where feasible run the relevant code path (in a scratch/sandboxed way) to confirm it's real, not stale, not a misunderstanding. Check the ask against roadmap/vision docs (ROADMAP.md, ARCHITECTURE.md, DECISIONS.md, MANIFEST.md) and note whether it's a scoped fix vs. a bigger direction-setting ask needing human scoping. Draft and post a `gh issue comment` with: confirmed findings with evidence, corrections to stale/wrong claims, a recommendation per CLAUDE.md's Recommendation Assessment mandate, and concrete test/verification steps for the fix. Report what you found and what you posted. ## Procedure ### 1. Fetch the issue Run `gh issue view <n> --json title,body,comments,labels,linkedPullRequests`. Extract: - Title and body (claims to verify) - All comments (context, earlier findings, clarifications) - Labels (priority, type, status si