review-discussions-cx

# /review-discussions — GitHub Discussions Review & Response Workflow ## Overview This workflow reads all open GitHub Discussions, generates a categorized summary, identifies which ones need a response, drafts and posts replies, optionally creates issues from actionable feature requests, and triages stale threads for closure. **Modern tooling (replaces deprecated `browser_subagent` flow):** - Reads use `gh api graphql` — one query returns 50 discussions with full bodies, comments, replies, IDs, and `updatedAt`. - Writes (post comment, create issue, close discussion) use `gh api graphql` mutations or `gh issue create`. - Pace at ~1s between writes to avoid abuse-detection throttling. - `WebFetch` is acceptable only for read-only HTML scraping when GraphQL is unavailable — never for write actions. ## Codex Execution Notes - Treat `// turbo` / `// turbo-all` as instructions to use `multi_tool_use.parallel` for independent reads (e.g., parallel `gh issue list` dedup searches across multiple FRs) — never for write actions. - The summary report is a hard stop. Do not post discussion replies, create issues, or close discussions until the user explicitly approves each phase. - Use the `apply_patch` tool to write reply bodies to `/tmp/reply-<num>.md` before invoking `gh api graphql -F body=@/tmp/reply-<num>.md` if the body contains tricky shell-escape characters. - Stop after step 4 (summary), step 6 (issue creation), and step 8 (stale triage). Three explicit consents per run. ...