report-issue

Override (this command only): The swe-workbench:product-manager agent's default rules "Does not pass --repo explicitly to gh issue create" (Decision boundaries) and "Never pass --repo" (Mutation rules) are suspended for /swe-workbench:report-issue. Every gh command in this flow that targets a repository MUST name lugassawan/swe-workbench explicitly and never infer it from the working directory — but each command takes the target in its own shape:

• gh issue … and gh label …: --repo lugassawan/swe-workbench.
• gh repo view: the repo as a positional argument. It does not accept --repo.
• gh api: the literal repos/lugassawan/swe-workbench/… path — never {owner}/{repo} placeholders, which resolve from the working directory. It does not accept --repo.
• gh auth status: host-scoped, takes no repo.

A command rejected with unknown flag means the command line is wrong — it is not a repo-access failure. No other rule is changed.

The user wants to file a plugin issue: $ARGUMENTS

Target repo (hardcoded): repo="lugassawan/swe-workbench"

---

Step 0 — Blank-argument routing

If $ARGUMENTS is empty, do NOT error. Instead:

Step 0a — Mode selector

Ask the user to choose a mode, then wait for the reply:

How would you like to find a plugin-related thought to report?

1. Quick pick — up to 3 raw candidates from this session/memory
2. Synthesize — aggregate all memory into ranked, themed enhancement insights

Reply with 1 (quick pick) or 2 (synthesize).

Reply 1 → Branch A — Quick pick. Reply 2 → Branch B — Synthesize.

Branch A — Quick pick

1. Scan the current conversation for actionable plugin-related thoughts: frustrations, lessons learned, complaints about plugin behaviour, feature ideas, or pain points. Collect up to 3 candidates with a one-line framing each.

2. If conversation yields fewer than 3, scan memory via the runtime:

   command -v swe-workbench-memory >/dev/null 2>&1 || {
     echo "swe-workbench runtime commands not on PATH — reinstall or update the swe-workbench plugin." >&2
     exit 1
   }
   RESULT=$(swe-workbench-memory show --as claude | swe-workbench-result-check swb.memory/1) || exit 1
   

   Read entries with printf '%s' "$RESULT" | jq -r '.data.entries[] | "\(.store) \(.name) \(.description)"' — entry order is the recency signal (index order, newest first; there is no date frontmatter). Read an entry's full body at its .data.entries[].path field — an absolute path resolved per entry by the runtime, so a worktree/cwd-slug merged entry points at the store it actually lives in. Collect additional candidates until you have up to 3, prioritising entries that mention the plugin, commands, agents, or skills by name.