Small and medium open-source repos accumulate bug reports and feature requests that sit open for months because nobody has time to triage them. Every maintainer knows the feeling of opening the Issues tab and seeing 40+ items with zero labels, zero triage, zero idea which ones are quick fixes and which ones are rabbit holes.
GitHub Issue Triage BYOK is a small WordPress plugin that gives you a wp-admin dashboard listing a repository's open GitHub issues, with a one-click "Generate fix proposal" button. Click it and an AI model reads the issue title and body and gives you back a likely root cause, a concrete fix, and a suggested test — you copy, adapt, and act on it yourself.
A few things it deliberately does NOT do:
- It never writes to GitHub, comments, labels, or opens pull requests. Read-only, always.
- It doesn't ship an API key of its own. BYOK (Bring Your Own Key): you plug in your own GitHub token and your own AI key (any OpenAI-compatible chat completions endpoint works, not just OpenAI).
- No subscription for the base functionality: the free version generates up to 20 AI fix proposals per month, which is enough to stay on top of a small/medium repo's queue. A one-time-payment Pro license removes the monthly cap if you need more.
Why WordPress and not a GitHub Action or a CLI tool? Because a lot of maintainers of small plugins/themes/tools already live in wp-admin for their own site, and having the triage dashboard one click away (rather than another terminal tab or CI log to check) is the difference between actually doing triage weekly and letting it pile up.
If you maintain a repo where issues outnumber your available time, it's on the WordPress plugin directory search and here: https://shop.lumnika.com/gh-issue-triage-byok.html
Happy to answer questions about the BYOK approach or how the fix-proposal prompt is built.
Top comments (0)