review-discussions-cx

Automatically triage open GitHub Discussions by fetching full thread content via GraphQL and building an actionable, categorized summary that groups threads by response state. This allows maintainers to quickly identify items needing first replies, follow-ups, or closure.

You can create tracking issues from GitHub Discussions feature requests with deduplication checks. The workflow proposes issue creation from actionable feature requests but requires explicit, interactive multi-phase consent before executing any write mutations.

Manage stale GitHub Discussions by detecting aging threads in Q&A or General categories and recommending soft-closure or pinging. The workflow drafts closing comments and applies safe handling rules only after receiving explicit user approval for the write operation.

Yes, drafting and posting replies requires manual approval. The workflow detects whether a discussion needs a first response or follow-up, drafts intent-specific replies, and enforces interactive, multi-phase consent gating before any writes are executed.

Automated responses handle GraphQL node IDs by enforcing correct mapping of node IDs for mutations. The workflow paces and verifies API results after writes to ensure GitHub GraphQL mutations execute safely and accurately during discussion triage.