For an overview of all available workflows, see the main README.
Automatically extract actionable tasks from GitHub Discussions and create trackable issues
The Discussion Task Miner workflow runs daily to scan recent GitHub Discussions for actionable improvement opportunities. It identifies concrete, well-scoped tasks and converts them into GitHub issues (up to 5 per run), bridging the gap between discussion insights and tracked work items.
# Install the 'gh aw' extension
gh extension install github/gh-aw
# Add the workflow to your repository
gh aw add-wizard githubnext/agentics/discussion-task-minerThis walks you through adding the workflow to your repository.
graph LR
A[Scan Recent Discussions] --> B[Extract Action Items]
B --> C[Filter & Prioritize]
C --> D{High Value?}
D -->|Yes| E[Create GitHub Issue]
D -->|No| F[Skip]
E --> G[Update Memory]
F --> G
The workflow reads discussions from the last 7 days, analyzes their content for recommendations, action items, and improvement suggestions, then converts the top findings into focused, actionable GitHub issues. It uses repo-memory to avoid re-processing the same discussions across runs.
GitHub Discussions must be enabled for your repository. The workflow works best in repositories that generate discussion content from other agentic workflows (such as analysis reports, quality audits, or review summaries), though it can also mine any human-authored discussions containing improvement suggestions.
Based on usage in the gh-aw repository: 57% merge rate (60 merged PRs out of 105 proposed through a discussion → issue → PR causal chain). The workflow demonstrates how insights buried in discussions can be surfaced as trackable work—a verified example chain: Discussion #13934 → Issue #14084 → PR #14129.
The workflow is configured to:
- Run daily
- Create max 5 issues per run
- Auto-expire issues after 1 day if not addressed
- Use repo-memory to track processed discussions and avoid duplicates
To customize which types of tasks to extract, edit the "Focus Areas" and "Task Extraction Criteria" sections in the workflow file. After editing, run gh aw compile to update the workflow and commit all changes to the default branch.
This workflow pairs especially well with other analysis workflows that post findings as discussions: