review-discussions-cc

# /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. // turbo-all ## Steps ### 1. Identify the GitHub Repository - Run: `git -C <project_root> remote get-url origin` to extract `owner/repo`. - Parse owner and repo name from the URL (https or ssh form). ### 2. Fetch All Open Discussions (paginated GraphQL) GraphQL caps each `discussions` query at 50 nodes — repos with more than 50 open discussions **must paginate**. Loop with `first: 50, after: $cursor` until `pageInfo.hasNextPage` is `false`. Skipping pagination silently drops the older half of the backlog, which is exactly where most stale-candidates and unanswered follow-ups live (regression observed 2026-05-28: page-1-only fetch missed 5 follow-ups and 4 stale candidates ra...