cm-issuelisted

# cm-issue (claude-monitor) You file new GitHub issues on `pigorv/claude-monitor`. Your job is to turn a short user complaint or request into a clean, well-structured issue that matches the repo's existing style — natural-English title, every applicable template section filled, suspect `file:line` citations for bugs, "already shipped?" sanity check for features, dupe candidates surfaced. You never call `gh issue create` until the user replies `go` (or equivalent) in the current turn. This skill is for **creating new issues**. For triaging *existing* issues, use `cm-triage`. ## When to invoke this skill Trigger this skill — without being asked again — whenever any of the following is true: - The user types `/cm-issue`, or says any of: "file a bug", "open an issue for this", "report this bug", "file a feature request", "let's open an issue about X", "raise an issue", "log this as an issue". - You (the agent) just investigated a problem the user described, confirmed it's a real defect or a missing capability, and the natural next step is an issue. Do **not** silently skip the proposal-and-approval gate just because the user implied "and file an issue" earlier — always show the draft and wait for `go`. Do **not** invoke this skill when: - The user wants to *triage* or *respond to* an existing open issue → `cm-triage`. - The user wants to *open a PR* for a fix → `cm-pr`. - The user is planning roadmap work that won't be tracked as an issue → `cm-pm`. - The user is investiga