review-discussions-cc

Triage GitHub Discussions by summarizing threads and drafting replies.

44.0k|5.9k|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/diegosouzapw/OmniRoute --skill review-discussions-cc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-discussions-cc
Source: https://github.com/diegosouzapw/OmniRoute/tree/main/.agents/skills/review-discussions-cc
Command: npx skills add https://github.com/diegosouzapw/OmniRoute --skill review-discussions-cc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps repository maintainers avoid missing important GitHub Discussions by automatically summarizing open threads, drafting appropriate responses, creating issues for actionable feature requests, and identifying stale conversations for closure.

Core Features & Use Cases

  • Unified Discussion Triage: Reads all open GitHub Discussions in batches and produces a categorized report grouped by pending action (needs response, follow-up pending, stale candidates, answered, resolved).
  • Action-Oriented Replies: Generates intent-specific draft replies (bug confirmation, feature request, support/config, thanks, and stale/closing) and posts them only after explicit user approval.
  • Issue & Closure Automation (with guardrails): Deduplicates feature requests by searching existing issues, creates new issues when approved, and recommends soft-close or reporter pings for stale threads while posting a closing comment first.

Quick Start

Use the review-discussions-cc skill to triage all open GitHub Discussions for your repository and return a summary report for approval before posting replies, creating issues, or closing stale threads.

Frequently Asked Questions about review-discussions-cc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage open GitHub Discussions automatically?

Automated GitHub Discussions triage involves reading open threads in batches, summarizing content, and producing a categorized report grouped by pending action needs response, follow-up pending, stale candidates, answered, or resolved.

Can I automatically create GitHub issues from feature requests in Discussions?

You can create GitHub issues from actionable feature requests in Discussions by performing deduplication against existing issues first, then executing issue creation mutations only after receiving explicit interactive user approval.

What is the best way to manage stale GitHub Discussions?

Managing stale GitHub Discussions requires identifying stale candidates, posting a closing comment first, then recommending soft-close or reporter pings, with all write actions gated behind explicit interactive user approval.

Does this GitHub Discussions triage workflow require the GraphQL API?

GitHub Discussions triage requires using GitHub GraphQL via gh API with node IDs for mutations, persisting fetch results for re-runs, and detecting attachments and languages across comments and replies.

How do I draft intent-matched responses for GitHub Discussions?

Drafting intent-matched responses for GitHub Discussions involves generating intent-specific replies for bug confirmation, feature requests, support configuration, thanks, and stale closing, posting them only after explicit user approval.