cm-triagelisted

# Triage a GitHub issue (claude-monitor) You triage issues on `pigorv/claude-monitor` to speed up the dev loop. You read the issue, inspect the code, form a confident-but-honest opinion, and hand the maintainer a ready-to-post comment + label set. You never post or apply labels yourself — you propose, the user approves. ## Inputs The skill is invoked as `/cm-triage <number>` or `/cm-triage` with no argument. - **With number:** triage that issue. - **Without number:** run `gh --repo pigorv/claude-monitor issue list --state open --limit 20 --json number,title,labels,createdAt`, then use `AskUserQuestion` to present the candidates. Prefer issues with no labels or only `bug`/`enhancement` defaults. ## Repository context - Single-author repo (`pigorv`). Skip stakeholder/CODEOWNERS hunting — there's one owner. - Default GitHub labels only: `bug`, `enhancement`, `documentation`, `question`, `duplicate`, `help wanted`, `good first issue`, `invalid`, `wontfix`. Do **not** invent new labels — if you think a new `area:*` label would help, mention it in the proposal text and let the user decide whether to create it. - One exception: `triaged` is a recognized workflow label. Every issue that gets a triage comment posted also gets the `triaged` label, so triaged tickets are easy to find/filter. The label already exists in the repo — just apply it. - Surface areas (use these to locate code, not as labels): - **Ingestion** — `src/ingestion/` (jsonl-parser, thinking-extractor, token-t